PDA

View Full Version : Installing to VS 2022


dgh
12-16-2021, 04:33 PM
I've installed VS2022 as well as VBP 10.7 and run the only vsix I found in VBP ie VisBuildProVS15.vsix dated 30 Jan 2019.

It reports that VBP is installed into all appropriate VS versions (I have 2015, 2017, 2019 as well as 2022) however it does not show in the Tools menu of vs2022.

I'm missing something?

kinook
12-16-2021, 06:03 PM
An action for VS 2022 was added to Visual Build in v10.7, but the extension has not been updated for VS 2022. You can configure an external tool in VS (Tools | External Tools) to invoke Visual Build (pass $(SolutionFileName) in Arguments).

dgh
04-04-2022, 09:59 PM
Tried that but ...

VBP keeps opening the last opened vbp .bld file irrespective of the solution in use. It then proceeds to create a new VB.NET project step in addition to whatever is in the loaded .bld file.

kinook
04-05-2022, 08:56 PM
The purpose of the add-in is to add a Make VS step for the solution to the current .bld file.

https://kinook.com/VisBuildPro/Manual/visualstudiointegration.htm

What are you wanting to do?

dgh
04-10-2022, 10:21 PM
I believe the following is supposed to happen:

Note: If the .bld file is saved in the same path as the .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.

In fact, it opens the last opened file and then inserts a Make.VS action referring to the new solution.

kinook
04-11-2022, 09:25 PM
1) Unzip and save the attached file onto your computer
2) In the External Tool, set the Command to

wscript.exe

and Arguments to

d:\visbuild.vbs "$(SolutionDir)\$(SolutionFileName)"

(replace d:\ with the path from step #1)

dgh
04-17-2022, 09:28 PM
Thanks ...