Reference third-party DLL in Visual Studio 2010 gives original DLL path? -
I would like to add a third party DLL to 4 from my source control, so that I do not have
I have copied the DLL file ( Microsoft.Expression.Interactions.dll ), install the Expression Blend (or maybe just SDK) on my build server. Code>) to
C: \ Program Files (x86) \ Microsoft SDK \ Expression \ Blend. NetFramework \ v4.0 \ libraries
and the file was checked in TFS at the root of my source.
However, if I reference the DLL fill ( C: \ source \ & project> project & gt; Microsoft.ExpressionInteractions.dll, copied through Visual Studio 2010 add context menu The DLL file retains the reference, but if I look at the properties window for reference, the path is the original DLL file path (i.e.,
C: \ Program Files (x86) \ Microsoft SDKs \ Expression \ Blend \ .NETFramework \ v4.0 \ Libraries \ Microsoft.ExpressionInteractions.dll
).
If I remove the DLL, the file works fine from the blend directory, but this is not a good solution, because I have other third party DLL files which I would like to add too, The program will be able to remove the control again and make sure to break a group.
The July 2010 edition of Productivity Power Tools for Visual Studio 2010 and inside my source tree Using the Browse button to find the DLL file.
Obviously, the "add context" functionality in the power tools tries to "be smart" by any means, which is meant for DLL files and changes the path for me.
The path is fine after trying to add DLL files to my laptop (where I do not have power tools installed)?
I think check it out a bit more ... but for now, it seems "answer".
Comments
Post a Comment