I use several devices which must connect to my Wndows 7 pc often. Some days ago, suddenly I did not succeed in coupling them to my pc. The problem seems to be security related. My solution:
- Open a command prompt window using elevated rights.
- Type the following command in the window: net localgroup Administrators local service /add
- Press Enter
- Done (at least, you should be)!
It is probably a little too agressive to solve the problem like I did, but I assume you can use this command as a work-around or as a reference for a better solution. In that last case, I would definitely like to see your solution in the comments section .
Lately I seem to use Twitter more than I use my blog. Keeping up on Twitter is easier than writing entire blog items . I just added the WP to Twitter plugin to my blog to notice my followers that I blog sometimes. Therefore, if you are interested in my short messages to the world as well ánd want to stay tuned with my progress at this blog, I hereby invite you to follow me: @loedeman.
Happy coding! Cheers!
I had to find the public key token for a strongly named assembly in .NET. Searching for a solution, I came along Wriju’s Blog. It appears the answer is very simple: use the .NET Framework tool ‘sn.exe’. Since I do not want to forget about this one, here it is:
- Open the Visual Studio <version reflecting DLL creator/signer> Command Prompt
- Point to the dll’s folder you want to get the public key
- Use the following command: sn –T myDLL.dll
This will give you the public key token. Of course this only works if the assembly is strongly signed .
It seems everyone I meet is struggling with software versioning. Although it should be fairly easy to deliver consistently versioned software, it almost always appears to be ‘nearly perfect’. And just that ‘nearly’ part makes it crappy and unreliable. However, there is light at the end of the tunnel : here is a great post about semantic versioning – the way you should do it: http://semver.org/.