Posts Tagged ‘Visual Studio’
I began having problems with the Axialis icon editing toolbar in Visual Studio a few weeks ago. It would appear as a short, empty, ugly little toolbar within Visual Studio. I would remove it, even delete it out of Visual Studio, and it still hung around and appeared there every time I started up. Fortunately for me, this problem has a simple fix.
If you’re using a x86 machine, edit the following within the registry:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\AddIns\IconWorkshopAddin.Connect
Set value CommandPreload to 0×00000000 (0).
If you’re using a x64 machine, edit the following within the registry:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\9.0\AddIns\IconWorkshopAddin.Connect
Set value CommandPreload to 0×00000000 (0).
http://www.axialis.com/forum/viewtopic.php?f=4&t=2179
The Problem
Lately I’ve been experiencing some frustrating problems with references to DLL files in a Visual Studio solution. Since I’m working with a team of other programmers, we are obviously using a code versioning system—in this case SourceSafe. It seems that nearly every time I “get the latest version” of the solution from SourceSafe and then try to build it, I will get errors with references to missing DLLs. However, the “missing DLLs” actually exist. The problem is that the references to these DLLs within the solution are wrong.
Because each of the other programmers have a different path to their own copies of the same solution, they also have different paths to the DLLs that are included in that solution. One programmer will notice that his stuff isn’t compiling, he’ll fix the reference error, check it in, and then simultaneously break it on all the other programmers’ machines (Or at least all those will a different file structure).
The Fix
To fix it, you’ll want to use “Reference Paths” within Visual Studio:
- In Solution Explorer, right-click your project node and click Properties. The Project Designer should appear.
- If you are using Visual Basic, select the References page and click the Reference Paths button. In the Reference Paths dialog box, type the path of the folder that contains the DLL that you want to reference in the Folder field, then click the Add Folder button. If you are using C#, select the Reference Paths page. In the Folder field, type the path of the folder that contains the item you want to reference, and then click the Add Folder button.
That’s it! Reference Paths are saved within each user’s own profile, so they will not be propagated to the other SourceSafe users when you check in your files. When you build a solution, Visual Studio will first try to find the DLL with the hardcoded path that is provided within the solution. If it can’t find it, then it will look within the Reference Paths for the file, where you should now have the correct reference to the DLLs.
http://msdn2.microsoft.com/en-us/library/ayds71se(VS.80).aspx