warrens

Hello,

We're interested in expanding our use of VSTS from our current Dev + TFS workgroup setup, to incorporate the Test edition as well. Since we only have MSDN subscriptions for the Dev edition, we're using the Team Suite 180-day trial to play around and see if it meets our needs.

Everything's working great on the developer machine side; we've built some tests and are happy with what we've got, but unfortunately, because our TFS build machine doesn't have the Test edition of VS installed, the necessary DLLs aren't installed, so we end up with a bunch of lines like this in our build logs:

C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : TestTypes\{37e36796-fb51-4610-8d5c-e00ceaa68b9f} could not be loaded because the TIP could not be instantiated for the following reason(s): Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.LoadTestPackage, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : TestTypes\{4e7599fa-5ecb-43e9-a887-cd63cf72d207} could not be loaded because the TIP could not be instantiated for the following reason(s): Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.LoadTestPackage, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
C:\Program Files\MSBuild\Microsoft\VisualStudio\v8.0\TeamBuild\Microsoft.TeamFoundation.Build.targets : warning : TestTypes\{7a24f8ff-85da-d664-ef44-83ff4743dae6} could not be loaded because the TIP could not be instantiated for the following reason(s): Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.Tips.ManualTest.Tip, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

We've also installed Buck Hodges' TestToolsTask since we don't want to spent a lot of time building out the metadata files, we just want to see it work.

That leads me to my question: How safe is it to uninstall Visual Studio from a build machine, then install the Team Suite demo for our evaluation purposes

Thanks in advance for any answers!



Re: Team Foundation Server - Build Automation Changing VS edition on a production build server

Matthew Mitrik MSFT

Hi Warrens,

Our dev team is currently very busy, but we should be able to address this next week.

Thanks for being patient,
-Matt






Re: Team Foundation Server - Build Automation Changing VS edition on a production build server

warrens

Hi Matt, thanks for the reply. Looking forward to any insights!

Warren.





Re: Team Foundation Server - Build Automation Changing VS edition on a production build server

Matthew Mitrik MSFT

((Moved to Build forum))




Re: Team Foundation Server - Build Automation Changing VS edition on a production build server

Ognjen Bajic

You shouldn't experience any special problems on deinstalling VS Dev Ed and installing Team Suite on the build machine. You could even only install Suite without previously deinstalling Team Dev.

See here (http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=122805&SiteID=1) for related question:

Q: If I use the Team Suite trial, what happens if I then install a role-based product
A: The Suite trial will continue to launch since it is considered the higher SKU. The trial edition will need to be uninstalled before you can use a role-based product.

You were right that the errors you listed come from the fact that Team Dev can deal with unit tests only.

Ognjen, VSTS MVP