Visual Studio integration - Use specified .bld file

[dgh]

So it will open a new VSBuild project every time

What's the friggin point of even having a VS Integration

[kinook]

The point of the add-in is to create a step for building the current solution. The idea was that this step would be incorporated into the overall build process (added to a .bld file that would perform others steps like retrieving from source control, building other solutions, updating versions, building installers, deploying to web sites, etc.), and until now we've never had any feedback requesting it to work differently.

It sounds like maybe what you want to do is save the .bld file in the same location as the .sln file, and then be able to re-open that .bld file later on to build just the current solution outside of VS?

[dgh]

Originally Posted by kinook

It sounds like maybe what you want to do is save the .bld file in the same location as the .sln file, and then be able to re-open that .bld file later on to build just the current solution outside of VS?

That sums it up very well. I use VSBuild extensively on all my projects and some of the built scripts do quite a few tasks. VSBuild saves me heaps of time and effort and I highly recommend all and sundry to use it.

I have in the past used one VSBUILD project to control all my VSBuild projects spread over 15+ dll's and programs. I know this sounds familiar This has suited me fine to date and I have had no real need to use the button on the VS Toolbar. I am now changing my methodology so that individual programs and in particular dll's can be compiled and distributed individually. The use of the VS button has now become an important function for me.

Keeping the auto re-load of the last project would also be important to me when running VSBuild from the command line/desktop however I would expect the VS button would act the way you describe. I presume some configuration of the buttons functionality would be included somewhere within the VS solution itself.

Can this be implemented in a short space of time, if at all

Thanks.

[kinook]

In the latest download, the addins/extensions for VS 2008 and later have been modified: If a .bld file is saved in the same path as a .sln file with the same base name (i.e., c:\full\path\xyz.bld and c:\full\path\xyz.sln), the add-in will open that .bld file instead of opening the previous .bld file (or creating a new project) and inserting a new step for the .sln file.