Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. Visual Basic
  4. Visual Basic 2005 deployment problem

Visual Basic 2005 deployment problem

Scheduled Pinned Locked Moved Visual Basic
questionsysadmindebugginghelp
6 Posts 3 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • R Offline
    R Offline
    RJGCarey
    wrote on last edited by
    #1

    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

    D S 2 Replies Last reply
    0
    • R RJGCarey

      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

      D Offline
      D Offline
      Dave Kreskowiak
      wrote on last edited by
      #2

      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

      R 2 Replies Last reply
      0
      • R RJGCarey

        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

        S Offline
        S Offline
        Sipder
        wrote on last edited by
        #3

        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.

        1 Reply Last reply
        0
        • D Dave Kreskowiak

          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

          R Offline
          R Offline
          RJGCarey
          wrote on last edited by
          #4

          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

          D 1 Reply Last reply
          0
          • R RJGCarey

            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

            D Offline
            D Offline
            Dave Kreskowiak
            wrote on last edited by
            #5

            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

            1 Reply Last reply
            0
            • D Dave Kreskowiak

              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

              R Offline
              R Offline
              RJGCarey
              wrote on last edited by
              #6

              Seems to work. Thanks for the help. RCarey

              RCarey

              1 Reply Last reply
              0
              Reply
              • Reply as topic
              Log in to reply
              • Oldest to Newest
              • Newest to Oldest
              • Most Votes


              • Login

              • Don't have an account? Register

              • Login or register to search.
              • First post
                Last post
              0
              • Categories
              • Recent
              • Tags
              • Popular
              • World
              • Users
              • Groups