Visual Basic 2005 deployment problem
-
For many years I have deployed my visual basic projects from my development computer to my production ones by copying the project's directory to the production computer. I then pin the project\bin\***.exe to the start menu. Works fine. Simple and quick. I can continue to debug on the production computer by running the project in DbgCLR.exe. I have now converted all to 2005. Confusion has arisen. I still have project\bin\****.exe; but now I've also got project\obj\debug\***.exe and project\obj\Release\***.exe. What the new ones for? Why does the debug .exe seem lag behind? Which is the proper one to run in production mode? I've Googled it. Not much to find. Thanks RCarey
RCarey
-
For many years I have deployed my visual basic projects from my development computer to my production ones by copying the project's directory to the production computer. I then pin the project\bin\***.exe to the start menu. Works fine. Simple and quick. I can continue to debug on the production computer by running the project in DbgCLR.exe. I have now converted all to 2005. Confusion has arisen. I still have project\bin\****.exe; but now I've also got project\obj\debug\***.exe and project\obj\Release\***.exe. What the new ones for? Why does the debug .exe seem lag behind? Which is the proper one to run in production mode? I've Googled it. Not much to find. Thanks RCarey
RCarey
Those are the Debug and Release build folders. In Debug, the code optimizations are turned off and a bunch of other debug information is output from the build process. In Release, the code optimizations are turned on and the outputs are stripped of all debugging information.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
For many years I have deployed my visual basic projects from my development computer to my production ones by copying the project's directory to the production computer. I then pin the project\bin\***.exe to the start menu. Works fine. Simple and quick. I can continue to debug on the production computer by running the project in DbgCLR.exe. I have now converted all to 2005. Confusion has arisen. I still have project\bin\****.exe; but now I've also got project\obj\debug\***.exe and project\obj\Release\***.exe. What the new ones for? Why does the debug .exe seem lag behind? Which is the proper one to run in production mode? I've Googled it. Not much to find. Thanks RCarey
RCarey
To do so you need to add new project of type "set up & deployment" in the current project. Then add all the output files to output directory then build it. Here the name of the folder can be specified that in which folder you want to save your exe and dependent fils? By default it is Debug folder. You can use any of you mentioned. it doesn't matter.
-
Those are the Debug and Release build folders. In Debug, the code optimizations are turned off and a bunch of other debug information is output from the build process. In Release, the code optimizations are turned on and the outputs are stripped of all debugging information.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Sounds like I should deploy by copying the Release\***.exe to another computer. Is this true? What is the purpose of the bin\***.exe file? Thanks RCarey
RCarey
You can copy it or you can add a Setup and Deployment project to your solution and create a installer for it. the \bin folder was were both the Debug AND Release builds ended up in previous versions of Visual Studio. The latest build overwrote the previous, no matter what the configuration. Now, with a folder for each build configuration, you can maintain various versions without overwriting the last build.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Those are the Debug and Release build folders. In Debug, the code optimizations are turned off and a bunch of other debug information is output from the build process. In Release, the code optimizations are turned on and the outputs are stripped of all debugging information.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007