By Scott Percy on
Friday, June 20, 2008 12:14 PM
As Gordon and I were working on a project together, we noticed that the version of an assembly we had set up was not the one that was being used in the application. We use a number of third party assemblies and controls, so keeping track of a specific version is crucial (especially, when that assembly references specific versions of other assemblies). Apparently, when you set up a reference to an assembly by selecting a file on your file system, Visual Studio may not choose that file when building. Actually, it only looks for that file based on the path as a second to last resort (the last being looking in the GAC). In fact, if you look at the properties of a referenced assembly, you'll see the "Path", but if you look at the XML of the project file, the property is called "HintPath". So, it's basically saying, "if you really can't find this file anywhere else, look here" instead of (what I thought it meant) "this is ...
Read More »