|
#1
|
|||
|
|||
No -- the Visual Build VS add-in always passes the name of the current solution to Visual Build.
You could create a custom external tool in VS to call Visual Build with a hard-coded solution filename (path+filename of visbuildpro.exe in the Command field and path+filename of the solution in the Arguments field). http://msdn.microsoft.com/en-us/libr.../76712d27.aspx |
#2
|
|||
|
|||
OK - thanks.
|
#3
|
|||
|
|||
The problem I am having is that when asked to save the changes it asks me for a filename, directory etc. I save that into the Projects root directory (<projectname>.bld) but starting up VSBuild from VS creates a new project each time.
|
#4
|
|||
|
|||
The latest build (VisBuildPro.exe 9.0.0.1) has been updated to re-open the last project when called from the Visual Studio add-in (if Tools | User Options | General | Reload last project at startup is checked).
|
#5
|
|||
|
|||
Quote:
When I click on the VSBuild menu item, it repeatedly opens a blank new VS project with MSBuild as the first item. Great - exactly what's supposed to happen according to the docs . Now, when I click on save, what directory do I chose to save it in and assuming your help file is correct then it will save it as <projectname>.bld. Unfortunately I don't know which directory to insert as none of them appear to be correct - I have saved it everywhere that is obvious to me. |
#6
|
|||
|
|||
Quote:
It doesn't matter which directory you save the .bld file in. |
#7
|
|||
|
|||
So it will open a new VSBuild project every time
What's the friggin point of even having a VS Integration |
#8
|
|||
|
|||
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? |
#9
|
|||
|
|||
Clarification please...
Quote:
If so, can this option (if it is an option) be disabled anywhere? I only want the VS -? VsBuild button to ever open the VSBuild project that 'belongs' to that specific VS project. Thanks. |
|
|