Quote:
Originally posted by kina
OK, so I managed to create (almost) all steps in VBProfessional.
How do I go from here?
How do I pack all this and then deploy to the next environment?
When I say Build, is some file created that I can just run on my QA environment?
Do I have to have VBP installed on it?
|
The depends on what deployment entails in your scenario. Some tasks can often be performed remotely from the build box (i.e., copying files, stopping/starting services, administering COM+ components, etc.). If some tasks must be performed locally on the deployment systems, you could either launch remote batch files, or you could install VBP there and build a VBP deployment project, depending on the complexity of the tasks involved.
Quote:
Also, I have a question in regards to Make VS.NET step.
When I click Test (or Build) on this step it actally opens MDE.
|
What is MDE? VBP launches another application instead of performing a build of the solution? Can you ZIP and post or send:
1) The info from Help | About | Install Info
2) The .bld file used to build
3) A build log file
4) The .sln file and project files being built (no source code files)
Quote:
We do not have VvStudio installed on QA so if it needs VBP needs it to run this step, this is not going to work.
|
You typically would only need to build on the build box and not deployment/QA machines. If you're using VS.NET 2002/2003, VS does need to be installed wherever you will build solutions. For VS2005, the .NET Framework v2.0 is all that's needed in most cases to build VS solutions/projects.