views:

18

answers:

1

I'd like to add a third party dll from Blend 4 to my source control, so taht I don't have to install Blend (or perhaps just til SDK) on my TFS Build server, in order to have a succesfull build.

I've copied the dll (Microsoft.Expression.Interactions.dll) from C:\Program Files (x86)\Microsoft SDKs\Expression\Blend.NETFramework\v4.0\Libraries to the root of my source and checked the file into TFS.

However, if I reference the copied dll (placed here: C:\Source\\Microsoft.ExpressionInteractions.dll) via the Add Reference menu in Visual Studio 2010 the dll gets reference allright, but if I look at the properties windows for the reference, the path point to the original dll path (ie. C:\Program Files (x86)\Microsoft SDKs\Expression\Blend.NETFramework\v4.0\Libraries\Microsoft.ExpressionInteractions.dll).

If I remove the dll from the Blend-directory it works fine, but that's not a good solution, as I have other third party dll's that I'd like to have added as well, a I'll loose control pretty quickly then and break a bunch of programs for sure.

A: 

I was using the July 2010 version of the Productivity Power Tools for Visual Studio 2010 and using the Browse button to locate my dll within my source tree.

Aprently the "Add Reference" functionality in the Power Tools somehow tries to "be smart" about referencing dll's and changed the path for me.

After trying to add the dll's on my laptop (where I don't have the Power Tools installed) the path is fine!!??

I think I'll have to investigate this a bit more... But for now, this seems to be "the answer".

kennethkryger