Any reason version 6.7a wouldn't work with Visual Studio 2010

[mbrock]

We are still on 6.7a of Visual Build Pro, and will be upgrading to Visual Studio 2010 in a few months. I know that VS 2010 is supported in 7.0+, but is there any reason it wouldn't work with 6.7a? Has anybody tried compiling VS 2010 projects with Visual Build Pro prior to release 7.0?

I realize ultimately we could make it work by having Visual Build Pro run batch files, but will the "Make VS" actions work with VS 2010?

[kinook]

Several changes were made to the Make VS.NET action in VBP v7 to support VS 2010.

[mbrock]

So I should take this to mean that when we do move to VS 2010, there's a good chance that our existing actions will no longer work?

[kinook]

Yes.

[mbrock]

Not the news I was hoping to hear, but thanks for your assistance!

[teognost]

Well,last time when we migrated from VS 2005 to VS 2008 -there was no problem -as discussed here:
http://kinook.com/Forum/showthread.php?s=&threadid=3806
I have also VBP 6.7a -so your point is as soon as our C# projects are migrated to VS 2010 -current VBP project will not work anymore?
And the only solution is to migrate VBP to latest version (7.5 I guess)?

[teognost]

kinook,could u pls confirm VS 2010 is not compatible with VBP 6.7a ?
I tried to compile a VS solution with VBP 6.7a -step "Make VS.Net "
and it worked although it launched devenv.com instead of msbuild.exe
However -if I specify the path to msbuild.exe -it is launched msbuild and not devenv.com

[kinook]

Several changes were made to the Make VS.NET action in VBP v7 to support VS 2010, so I doubt that v6.x is fully compatible with it.

[teognost]

ok,we bought the licence for upgrading to 7.5.
Do I need to change sthing into my existing projects or new version will automatically transform them?

[kinook]

You will need to upgrade your solutions to VS 2010 (by either opening in the VS IDE or automating the upgrade via Visual Build-- see http://www.kinook.com/VisBuildPro/Ma...olutiontab.htm), but you shouldn't need to change your Make VS steps to build once converted.

[wellilein]

@Moderator: does this apply only to Make VS.NET steps (upgrading the SLN file is sufficient) or does this also apply to Make VS 2005 and Make VS 2008 steps?
In other words: if I was version specific in my (old) build script, will I need to update all version specific build steps?

Is there a conversion tool which upgrades from Make VS 200x to 2010 (Actually the build script is XML, so there might be a XSL transformation)?

[kinook]

The Make VS* actions are all aliases for the same action, so they don't need to be updated. You could use the Replace in File action, the Write XML action, or possibly the Transform XML Log action to update the action name in your .bld files if desired.

[wellilein]

Didn't know they are aliases. Thank you, I will replace them using a text editor or something similar.