Every time I have need to determine the Windows version (eg. XP, Vista, Server 2008 etc) based on the Windows version number, I get surprised by how difficult it is to find this information on microsoft.com. The information is there, but it's fragmented, and I have to check at least 2-3 different source to get the full picture.
Now I am tired of this and have created a full list of Windows version numbers which should represent the full picture:
This is more a note-to-self than anything else, but making git work on non-default ssh port without cleaning and reconfiguring your local repo was not quite as straight forward as I thought. The config change is not related to GIT but to SSH actually!
Leave your local config file .git as they were, and go to:
Here you add a file named config where you specify your server name and port. In case you have multiple repos, or several ssh ports on the same server you have a problem (Or you have to manipulate your windows hosts file).
The SSH config file should now contain the following info:
Ever had the need to update a release with a minor change to one dll? These steps allow you to update a single dll in a installation from msi etc. Note that all steps are necessary to avoid problems with mismatch in dll references, manifests etc. Trying to update a single dll without these steps normally results in the following error:
Could not load file or assembly MyAssembly, Version=220.127.116.11, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
To avoid these kind of problems you have to make sure your dll's have the correct versions, and that all references are to the correct versions of all the assemblies (Normal problem whene using "1.0.*" as AssemblyVersion"
- Open you Visual Studio solution for the point of the release or todays date if there are no or few changes in the dll you want to update.
- Add you fix or change to your source code
- Go to references in the project you want to update (called project A)
- Delete all the references to projects in your solution (remember the names)
- Copy the same dll's from step 3 som programfiles or wherever you have the release installed. Copy the dll's to the bin/release folder of project A.
Struggled with following error yesterday:
The request failed with HTTP status 407: Proxy Authentication Required (The ISA Server requires authorization to fulfill the request. Access to th Web Proxy filter is denied)
I guess I am not the only one annoyed by the fact that I could not open Visual Studio by double-clicking a solution file. Finally I looked into this problem and first found a simple, but not satisfying solution:
By setting Visual Studio to not run as an administrator. But if you ever tried running Visual Studio on Windows 7 without admin rights, you know this is not a satisfying solution!
For the second time this week, I saw that my Squeezebox Server won't scrobble my played (and loved) tracks to last.fm! I started investigating, and in the server log of my Squeezebox server, I found the following errors:
I have really struggled with my Office 2010 Technical Preview the last few days. Most of the Office 2010 is working really good, but accessing word and excel documents located on a Sharepoint 2007 server, has not been easy!