2,892 questions
Visual Studio 2019 Solution does not create Two .EXE Output Files
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 31%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EF%3C/text%3E%3C/svg%3E)
Farkler
211
Reputation points
Recently converted a VB.NET solution from Visual Studio 2013 4.0 Framework to Visual Studio 2019 4.8 Framework.
The solution contains 22 projects. Of the 22 projects there is one Windows Form Application and one Windows Service project.
In Visual Studio 2013, compiling the solution would create two .exe files. One .exe for the Windows Form project and another .exe for the windows service project.
After converting to Visual Studio 2019 and compiling the solution, there is only one .exe file being created. That .exe file is for the Windows Form project which is the 'startup' project.
When solution was being compiled by VS 2013, both .exe files would get created.
Does anyone know what I need to do to get VS 2019 to create the two .exe output files when compiling? Thanks
Developer technologies VB
{count} votes
-
Karen Payne MVP 35,586 Reputation points Volunteer Moderator2021-03-26T14:38:03.613+00:00 Have you confirmed that Build is checked for both in
Configuration Manager(right click solution explorer top node for this)? Do the same forbat build
-
Farkler 211 Reputation points
2021-03-26T15:08:23.607+00:00 Hi Karen, Confirmed the project is checked in configuration manager. I do not have the "batch build" option? See attached image.
-
Karen Payne MVP 35,586 Reputation points Volunteer Moderator
2021-03-26T15:24:32.13+00:00 Okay, seems that Microsoft does not support Visual Basic projects in VS2019, see this page.
-
Farkler 211 Reputation points
2021-03-26T15:42:53.853+00:00 Thank you, I didn't see that Visual Basic projects were not supported. I wonder why this worked in Visual Studio 2013 but no longer in Visual Studio 2019? The project types have not changed. I appreciate your help.
-
Farkler 211 Reputation points
2021-03-26T16:19:08.56+00:00 Thanks, This won't be a problem for the developers working locally in their IDE. Is there a way we can enforce the Devops Pipeline to create both .exe files? Appreciate your help.
-
Viorel 122.5K Reputation points2021-03-26T16:55:16.297+00:00 I think that Batch Buld is not required. If a solution includes several projects, then all will be built. Make sure again that the projects are selected in Configuration Managed dialog for all of configurations (Debug, Release) and platforms. (Do you have several platforms?). Before build, select the active configuration and platform. Also make sure that there are no compilation errors.
-
Karen Payne MVP 35,586 Reputation points Volunteer Moderator
2021-03-26T16:56:46.837+00:00 Don't know only builds I do are Google -> Git (TypeScript) ->Git actions
-
Farkler 211 Reputation points
2021-03-26T17:39:54.663+00:00 "If a solution includes several projects, then all will be built"
Not all projects are being built. The Window forms project that is also the startup project and the DLL projects are being built. The Windows Service project in the solution is not being built.
I have confirm build order and build is 'checked' in configuration manager.
Also, setup an Azure Pipeline which is also only creating the one EXE and the DLL files. The Pipeline is not creating the Windows Service project EXE either.
Very odd. This all worked in Visual STudio 2013 and Team Foundation Build Controller.
-
Viorel 122.5K Reputation points
2021-03-26T18:10:24.313+00:00 Did you try to rebuild or build the Service project only, in Visual Studio? Check the Output window too, and also the output folder of this project according to its properties.
-
Farkler 211 Reputation points
2021-03-26T18:25:59.643+00:00 Hi Viorel-1, If i build only that project it does create the EXE file from Visual STudio 2019. For some reason it just doesn't do when building the entire solution.
We can probably live with that behavior if I could only get the Devops Pipeline to build both EXE files. That is a bigger problem for us, but I assumed if I figured it out in Visual Studio that any change would apply to the Pipeline.
I appreciate your help.
Sign in to comment
Sign in to answer