Quote:
Originally posted by trailway
First, thank for your help and rapid responses. I appreciate it.
I did the following:
1) Deleted my custom VisBuildPro.macros. Actually I removed all the Kinook files under 'Program Data'
2) Removed Visual Build
3) Reinstalled Visual Build
If you click on "Visual Studio & .NET Macros" in Help under Actions/Microsoft the article states that DOTNET_DIR, DOTNETSDK_DIR, and DEVSTUDIO_NET_DIR should all point to the highest versions of the respective utilities. I find that to be true except for DOTNETSDK_DIR which points to v6.1 versus v7.0a which the latest on my system. Is this wrong? Should I patch this on my system?
|
With previous SDKs, this registry value would be updated with the SDK path:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\CurrentInstallFolder
It appears this isn't happening with v7.0a (and I don't see another value that defines the current version), so you will need to manually update the path in the macro value.
Quote:
|
The other thing I want to say that I think that there is a fundamental design problem with the Team Test step, i.e. it needs to be redesigned to be Visual Studio version (or framework) specific. The fundamental issue relates to moving to the 4.0 CLR framework. What happens when a customer has existing bld files which run against Visual Studio 2008 and then moves to Visual Studio 2010? In this case they must go back and manually edit the old Team Test build steps to use the old MSTest. Confusing? I think so.
|
Some users are probably happy if they
don't need to update the step when upgrading to VS 2010. At any rate, you don't need to change the steps, just update the global DEVSTUDIO_NET_DIR global macro as needed (or define a project or temporary macro of the same name to override within a project or to switch between versions).