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. The Lounge
  3. VS6, VS.NET & VS.NET 2003

VS6, VS.NET & VS.NET 2003

Scheduled Pinned Locked Moved The Lounge
visual-studiocsharptutorialworkspace
8 Posts 5 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.
  • J Offline
    J Offline
    jelaft
    wrote on last edited by
    #1

    I've spent a lot of time recently trying to migrate a LARGE - 80 project, 200 MB source code - workspace from VC6 to VS.NET 2003. It hasn not been a fun experience; maybe I'm looking in the wrong place for stuff, but it annoys that what was a very good GUI has been broken. Anyway, the point is that I can't find a VS IDE section on CP so that people can post hints on how to migrate, and the explore new features that are hidden in there - I can't be the only one going through this pain ! So Chris, pls pls pls can we have one ! Thanks

    A D B 3 Replies Last reply
    0
    • J jelaft

      I've spent a lot of time recently trying to migrate a LARGE - 80 project, 200 MB source code - workspace from VC6 to VS.NET 2003. It hasn not been a fun experience; maybe I'm looking in the wrong place for stuff, but it annoys that what was a very good GUI has been broken. Anyway, the point is that I can't find a VS IDE section on CP so that people can post hints on how to migrate, and the explore new features that are hidden in there - I can't be the only one going through this pain ! So Chris, pls pls pls can we have one ! Thanks

      A Offline
      A Offline
      Anders Molin
      wrote on last edited by
      #2

      VS.NET IDE Issues: Here[^] - Anders Money talks, but all mine ever says is "Goodbye!" http://SourceLocker.net[^] SourceControl and DefectTracker Project. nsms@spyf.dk <- Spam Collecting ;)

      J 1 Reply Last reply
      0
      • A Anders Molin

        VS.NET IDE Issues: Here[^] - Anders Money talks, but all mine ever says is "Goodbye!" http://SourceLocker.net[^] SourceControl and DefectTracker Project. nsms@spyf.dk <- Spam Collecting ;)

        J Offline
        J Offline
        jelaft
        wrote on last edited by
        #3

        Sorry. D'oh ! :)

        1 Reply Last reply
        0
        • J jelaft

          I've spent a lot of time recently trying to migrate a LARGE - 80 project, 200 MB source code - workspace from VC6 to VS.NET 2003. It hasn not been a fun experience; maybe I'm looking in the wrong place for stuff, but it annoys that what was a very good GUI has been broken. Anyway, the point is that I can't find a VS IDE section on CP so that people can post hints on how to migrate, and the explore new features that are hidden in there - I can't be the only one going through this pain ! So Chris, pls pls pls can we have one ! Thanks

          D Offline
          D Offline
          Daniel Turini
          wrote on last edited by
          #4

          jelaft wrote: 80 project, 200 MB source code When your VS.NET software breaks the 10~20 project barrier, you begin to question the use of the word "Solution" to define project groups.

          // Quantum sort algorithm implementation
          while (!sorted)
          ;

          J 1 Reply Last reply
          0
          • D Daniel Turini

            jelaft wrote: 80 project, 200 MB source code When your VS.NET software breaks the 10~20 project barrier, you begin to question the use of the word "Solution" to define project groups.

            // Quantum sort algorithm implementation
            while (!sorted)
            ;

            J Offline
            J Offline
            jelaft
            wrote on last edited by
            #5

            Sigh :-( Yes, 80 projects is kinda stupid to have in one workspace / solution. However, we are burdened with lots of old code that we don't have the resouce to "rationalise" at the moment. At a rough guess we could probably get rid of about a 3rd of it. Even worse, some projects which are massively templated have started generating internal compiler errors in VS.NET. I've tracked this down in at least one case to sloppy coding where an operator=() method was declared on a templated class with no return type, but it's a needle in a haystack to find. Thanks

            G D 2 Replies Last reply
            0
            • J jelaft

              I've spent a lot of time recently trying to migrate a LARGE - 80 project, 200 MB source code - workspace from VC6 to VS.NET 2003. It hasn not been a fun experience; maybe I'm looking in the wrong place for stuff, but it annoys that what was a very good GUI has been broken. Anyway, the point is that I can't find a VS IDE section on CP so that people can post hints on how to migrate, and the explore new features that are hidden in there - I can't be the only one going through this pain ! So Chris, pls pls pls can we have one ! Thanks

              B Offline
              B Offline
              Brian Delahunty
              wrote on last edited by
              #6

              200 MB of sourcecode in one workspace?!?!?! :wtf: are u doing? Regards, Brian Dela :-)

              1 Reply Last reply
              0
              • J jelaft

                Sigh :-( Yes, 80 projects is kinda stupid to have in one workspace / solution. However, we are burdened with lots of old code that we don't have the resouce to "rationalise" at the moment. At a rough guess we could probably get rid of about a 3rd of it. Even worse, some projects which are massively templated have started generating internal compiler errors in VS.NET. I've tracked this down in at least one case to sloppy coding where an operator=() method was declared on a templated class with no return type, but it's a needle in a haystack to find. Thanks

                G Offline
                G Offline
                Giles
                wrote on last edited by
                #7

                jelaft wrote: Even worse, some projects which are massively templated have started generating internal compiler errors in VS.NET. I've tracked this down in at least one case to sloppy coding where an operator=() method was declared on a templated class with no return type, but it's a needle in a haystack to find. VC7 picks up on things that VC6 let pass. I've seen some shockers from some code I inherited where I'm surpised the thing worked properly. Only noticed them when I upgraded. You can tell once you start using it the compiler in VC7 is a big improvement, though people tend to pass over this and start complaining about the class wizard not being there. Now I've used it I much prefer the new method.


                "Je pense, donc je mange." - Rene Descartes 1689 - Just before his mother put his tea on the table. Shameless Plug - Distributed Database Transactions in .NET using COM+

                1 Reply Last reply
                0
                • J jelaft

                  Sigh :-( Yes, 80 projects is kinda stupid to have in one workspace / solution. However, we are burdened with lots of old code that we don't have the resouce to "rationalise" at the moment. At a rough guess we could probably get rid of about a 3rd of it. Even worse, some projects which are massively templated have started generating internal compiler errors in VS.NET. I've tracked this down in at least one case to sloppy coding where an operator=() method was declared on a templated class with no return type, but it's a needle in a haystack to find. Thanks

                  D Offline
                  D Offline
                  Daniel Turini
                  wrote on last edited by
                  #8

                  jelaft wrote: I've tracked this down in at least one case to sloppy coding where an operator=() method was declared on a templated class with no return type, but it's a needle in a haystack to find. I have this problem with templates that use forward-declared classes. None of them compiled, until I workarounded it passing the class as a template parameter with a default (uglier seeing than only talking).

                  // Quantum sort algorithm implementation
                  while (!sorted)
                  ;

                  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