Results 1 to 3 of 3
  1. #1
    3 Star Lounger
    Join Date
    Jul 2001
    Location
    Minneapolis, Minnesota, USA
    Posts
    299
    Thanks
    0
    Thanked 0 Times in 0 Posts
    I got some handy dandy solution from someone but despite the fact that they swore it was in 2008, it's 2005. Apparently they also set up some fancy references. The bad part is when I open it in 2008, MS insists on converting it and, you guessed it, the fancy references go away. Before I spend hours trying to read code in notepad, does anyone have a link/advice/hug for me?
    Carpy Diem, it's .

  2. #2
    New Lounger
    Join Date
    Sep 2009
    Posts
    13
    Thanks
    0
    Thanked 0 Times in 0 Posts
    [quote name='garbsmj' post='792540' date='08-Sep-2009 11:40']I got some handy dandy solution from someone but despite the fact that they swore it was in 2008, it's 2005. Apparently they also set up some fancy references. The bad part is when I open it in 2008, MS insists on converting it and, you guessed it, the fancy references go away. Before I spend hours trying to read code in notepad, does anyone have a link/advice/hug for me? [/quote]

    When you say fancy references, what are you referring to? Are you talking about references to third-party DLLs? Are you saying this was a project created in Visual Studio 2005 that you're trying to open in VS2008? What type of project, web, windows, console?

    I do not like using the conversion wizard because it will arbitrarily make choices for you about which changes to make to the code. If I have a project I want to migrate, if it's small enough, I merely create a new project in VS2008 and add the files to the project in explorer. But first, make a copy of your original VS2005 project first.

  3. #3
    3 Star Lounger
    Join Date
    Jul 2001
    Location
    Minneapolis, Minnesota, USA
    Posts
    299
    Thanks
    0
    Thanked 0 Times in 0 Posts
    [quote name='theUnGuru' post='792560' date='08-Sep-2009 13:09']When you say fancy references, what are you referring to? Are you talking about references to third-party DLLs? Are you saying this was a project created in Visual Studio 2005 that you're trying to open in VS2008? What type of project, web, windows, console?

    I do not like using the conversion wizard because it will arbitrarily make choices for you about which changes to make to the code. If I have a project I want to migrate, if it's small enough, I merely create a new project in VS2008 and add the files to the project in explorer. But first, make a copy of your original VS2005 project first.[/quote]

    Ya, I hate the conversion wizard too.

    This is a third part solution and after struggling with it, I pinpointed it down to SOAP commands (I know, there are thousands of websites devoted to this subject), and an interesting reference to a .dll that doesn't exist. I think I can fix the SOAP thing since I built something in VS2008 that calls SOAP, even though it's "deprecated". Anyway, thanks for the suggestion - this whole thing reminds me of a bad MS Access migration.
    Carpy Diem, it's .

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •