As a part of my build, I need to build a couple of Visual Studio (2005) deployment projects. Unfortunately, MSBuild can’t build deployment projects, so I need to launch devenv from within FB to build this solution.
I’m having trouble getting it to work though - I’ve configured a “Execute Program” action with the full path to devenv.exe, set the working directory to the location of the .sln file, and supplied appropriate command-line arguments to devenv. When I build though, I get a single cryptic error “Program returned error code : 1”. Indeed, it looks like devenv didn’t build the solution, since there’s no installer in the output directory.
Any idea what’s wrong? I’ve tried launching FB4 from a “visual studio 2005 command prompt” so that the environment is fully set up, but that didn’t make any difference (nor should it - VS launched by Explorer doesn’t have that environment, after all).
-cd
Nevermind :) I figured it out - there were files missing from the directory where the deployment project expected them to be. When I tested from the command line earlier, I had manually created the missing files, so naturally it worked.
Now to get something into the build to create those missing files...
Glad to hear you sorted it out.
You should also be able to use the “VS.NET Build Solution” action, unchecking the “Use MSBuild” property.
What package is that action in, and where does it appear in the Action Types list? I looked high and low through the actions for something like that and never found it (I may have the package unloaded, but looking through the package manager, I didn’t see anything that looked inappropriate).
Hi Carl,
Sorry, the action is called “Build VS.Net Solution”. It’s in the Compilers category.
The easiest way to find it is to start typing the name of the action in the filter (you can focus the filter with Ctrl-i)
If you still can’t find it, make sure you have the package “FinalBuilder 4.x VisualStudio .Net Support” loaded.
Thanks - I see it now. I guess there’s just enough things in the list that I was able to read past it the several times I looked for it. I’ll change to using that action tomorrow - it’s a better solution.
I switched to the "Build Vs.Net solution" action - that works great, thanks!