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
  1. Home
  2. General Programming
  3. Visual Basic
  4. vb .net - Moving to a new computer

vb .net - Moving to a new computer

Scheduled Pinned Locked Moved Visual Basic
csharpvisual-studiodebuggingquestion
4 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.
  • N Offline
    N Offline
    No e
    wrote on last edited by
    #1

    I have been using VS2008 on XP for some time now, converting a project to VB.net. I have it largely converted and am debugging now (i.e. the project is running fine) I am trying to move it to Windows 7 (finally). I installed the exact same visual studio I am using on XP, and I copied the project directory from the old computer to the new computer. For some reason I loose a few references so on the reference page I add them back in, there were three of them, all custom references. The reference dialogue tells me it can not find the files specified, on the XP machine they are listed as being in \project\obj\release directory, so on the Windows 7 machine I point to them there (not sure if I should do that or point to the original) When I try to run or debug the project I get the following errors and it stops. A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in MBIG.exe A first chance exception of type 'System.TypeInitializationException' occurred in MBIG.exe A first chance exception of type 'System.TypeInitializationException' occurred in MBIG.exe A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in MBIG.exe The program '[2776] MBIG.vshost.exe: Managed' has exited with code 0 (0x0). Anyone have any suggestions as to what I should do to resolve or identify the problems? (not sure it the references impact this or not) no-e

    D 1 Reply Last reply
    0
    • N No e

      I have been using VS2008 on XP for some time now, converting a project to VB.net. I have it largely converted and am debugging now (i.e. the project is running fine) I am trying to move it to Windows 7 (finally). I installed the exact same visual studio I am using on XP, and I copied the project directory from the old computer to the new computer. For some reason I loose a few references so on the reference page I add them back in, there were three of them, all custom references. The reference dialogue tells me it can not find the files specified, on the XP machine they are listed as being in \project\obj\release directory, so on the Windows 7 machine I point to them there (not sure if I should do that or point to the original) When I try to run or debug the project I get the following errors and it stops. A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in MBIG.exe A first chance exception of type 'System.TypeInitializationException' occurred in MBIG.exe A first chance exception of type 'System.TypeInitializationException' occurred in MBIG.exe A first chance exception of type 'System.Runtime.InteropServices.COMException' occurred in MBIG.exe The program '[2776] MBIG.vshost.exe: Managed' has exited with code 0 (0x0). Anyone have any suggestions as to what I should do to resolve or identify the problems? (not sure it the references impact this or not) no-e

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

      Add those .DLL's projects to this one and you can add a project reference instead of a file reference. That way, the .DLL projects will be recompiled (if needed) and any changes automatically propogate through to your application without screwing up the references. You will also have to go back to those .DLL's projects and make sure they compile and work as intended. They might have dependencies that have changed on Windows 7 or on projects you have no copied over. Judging by the error messages you posted, the .DLL's you're referencing may need to be registered on the machine, i.e: REGSVR32.

      A guide to posting questions on CodeProject[^]
      Dave Kreskowiak

      N 1 Reply Last reply
      0
      • D Dave Kreskowiak

        Add those .DLL's projects to this one and you can add a project reference instead of a file reference. That way, the .DLL projects will be recompiled (if needed) and any changes automatically propogate through to your application without screwing up the references. You will also have to go back to those .DLL's projects and make sure they compile and work as intended. They might have dependencies that have changed on Windows 7 or on projects you have no copied over. Judging by the error messages you posted, the .DLL's you're referencing may need to be registered on the machine, i.e: REGSVR32.

        A guide to posting questions on CodeProject[^]
        Dave Kreskowiak

        N Offline
        N Offline
        No e
        wrote on last edited by
        #3

        Dave, Thanks for the response, that appears to have put me in the right direction. I registered them, deleted interop.XXX files in question, added references to the proper dll files and it worked for two, it appears that it creates the interop.xxx files in the \obj\debug and \obj\release directories... at least for two of them. When I debug, it tells me it cant find the "interop.xxx3" file. If I look at references it lists the original DLL file for the one it can't find (the other two changed to indicate the interop.XXX and interop.xxx2 Can you give me a bit of guidance on how this is supposed to work? I could not find much in the way of background on the web. Is there a way to force it to create these files? no-e

        L 1 Reply Last reply
        0
        • N No e

          Dave, Thanks for the response, that appears to have put me in the right direction. I registered them, deleted interop.XXX files in question, added references to the proper dll files and it worked for two, it appears that it creates the interop.xxx files in the \obj\debug and \obj\release directories... at least for two of them. When I debug, it tells me it cant find the "interop.xxx3" file. If I look at references it lists the original DLL file for the one it can't find (the other two changed to indicate the interop.XXX and interop.xxx2 Can you give me a bit of guidance on how this is supposed to work? I could not find much in the way of background on the web. Is there a way to force it to create these files? no-e

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          Not sure about the full answer but when moving projects in this way you should only move the directories containing source code, and rebuild everything from scratch in the new location. Try doing a clean of your project, delete all obj and bin directory trees, reset all references to ensure they point to the correct DLLs on the new machine, check your project dependencies (if any), and then try building the project(s) again.

          speaking as ...

          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