We are currently investigating the use of VSS 2005 in a small development group however we have ran into some rather strange behavior. I would like to see if anyone else has had simular issues.

It looks as if the VSS-plugin team and the Visual Studio 2005- ide team are both using the "Copy Local" property of dependent references in different ways.

In the Visual Studio 2005 debug world this setting is asking if you want to copy over dependent references ( like dll's) into your debug directory. Thus you don't need to do a bunch of tricky stuff during the debugging phase of development.

However in the VSS-plugin world this setting is being used to indicate if you would like to copy the source code of the reference project below the current solutions directory. The issue with this is that if you have more than one application solution, you end up with duplicate files all over.

I've tried discussing this issue with Microsoft, but their tech didn't have the English language skills to really understand the problem. At this point I'm strongly looking at using Team Foundation Server.

I would really appriciate any comments/help.

Thanks!

Cody

Was this an MSDN support subscription call or a purchased support call? If it was you can ask to talk to others...also its up to the client, you, to specify if the result is closed or not. I have never had such a problem with support, at least MSDN....the general support may be differnt.

Was this an MSDN support subscription call or a purchased support call? If it was you can ask to talk to others...also its up to the client, you, to specify if the result is closed or not. I have never had such a problem with support, at least MSDN....the general support may be differnt.

This was/is a MSDN support subscritption call.

Then you should be able to not close it and move it up the chain. Good luck.

Well at this point I think the game plan is to not use VSS and purchase Team Foundation Server. However I just wanted to check and see if anyone had words of wisdom.

Thanks,

Cody