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. VS .NET

VS .NET

Scheduled Pinned Locked Moved The Lounge
csharpcssvisual-studio
14 Posts 12 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.
  • C Offline
    C Offline
    CSharpDavid
    wrote on last edited by
    #1

    Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

    J C E R A 9 Replies Last reply
    0
    • C CSharpDavid

      Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

      J Offline
      J Offline
      James T Johnson
      wrote on last edited by
      #2

      I was running Beta 1 on a P3 650, though it wasn't very stable it was livable. Since then I upgraded to a TBird 1GHz though :-D I've also increased how much RAM my computer had from 384MB to 1.5GB. James Sonork ID: 100.11138 - Hasaki "Smile your little smile, take some tea with me awhile. And every day we'll turn another page. Behind our glass we'll sit and look at our ever-open book, One brown mouse sitting in a cage." "One Brown Mouse" from Heavy Horses, Jethro Tull 1978

      1 Reply Last reply
      0
      • C CSharpDavid

        Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

        C Offline
        C Offline
        Chris Maunder
        wrote on last edited by
        #3

        I was running beta 2 on my 450MHz laptop, 128Mb RAM running W2K server and SQL Server 2000. Once it got up and running (you can do it! C'mon! load up!) it ran fine. I've now got it on a 850MHz with 256Mb and it's fine. No problems whatsoever. cheers, Chris Maunder

        A 1 Reply Last reply
        0
        • C CSharpDavid

          Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

          E Offline
          E Offline
          Eddie Velasquez
          wrote on last edited by
          #4

          I have VS.NET Enterprise Architect on a AthlonXP 1800+, 512M ram and plenty of hard drive space on Windows XP. In my machine it runs way faster that VS6.


          Eddie Velasquez: A Squeezed Devil (Don't you just love that anagram craze?)
          Checkout GUIDGen.NET

          1 Reply Last reply
          0
          • C CSharpDavid

            Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

            R Offline
            R Offline
            Ravi Bhavnani
            wrote on last edited by
            #5

            Looks like just the thing my 1.6GHz 768Mb 80Gb Dell needs to bring it to its knees. :) /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com

            1 Reply Last reply
            0
            • C CSharpDavid

              Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

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

              I'm using it at home on a PIII 600MHz with 512MB ram, and at work on a P4 1.3GHz with 256 MB ram. Both places it runs perfectly good. Actually it runs a bit better on my home pc, but I guess that's because it have more ram, and some fast SCSI-disks :) - Anders Money talks, but all mine ever says is "Goodbye!"

              1 Reply Last reply
              0
              • C Chris Maunder

                I was running beta 2 on my 450MHz laptop, 128Mb RAM running W2K server and SQL Server 2000. Once it got up and running (you can do it! C'mon! load up!) it ran fine. I've now got it on a 850MHz with 256Mb and it's fine. No problems whatsoever. cheers, Chris Maunder

                A Offline
                A Offline
                Andrew Peace
                wrote on last edited by
                #7

                You ran Win2k Server on a laptop :omg:? I found it okay on my old 35mhz k6-2 (upgraded since, however). [edit] I mean my 350mhz k6-2. Now that would've been sloooowwwwww :D. -- Andrew.

                C 1 Reply Last reply
                0
                • C CSharpDavid

                  Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

                  R Offline
                  R Offline
                  Rama Krishna Vavilala
                  wrote on last edited by
                  #8

                  P4 1.6 Mhz 512 RAM But I have to restart it from time to time. If you are doing intense debugging (Mixed mode) with debug symbols insalled for all the system files debugging becomes very slow. So from time to time I have to remove debug symbols from g:\windows\system32 and copy them back

                  1 Reply Last reply
                  0
                  • C CSharpDavid

                    Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

                    C Offline
                    C Offline
                    CSharpDavid
                    wrote on last edited by
                    #9

                    I have noticed I've only got 128MB, do you think 600MHz and 128MB is a bad combination????????

                    T 1 Reply Last reply
                    0
                    • C CSharpDavid

                      I have noticed I've only got 128MB, do you think 600MHz and 128MB is a bad combination????????

                      T Offline
                      T Offline
                      Tomasz Sowinski
                      wrote on last edited by
                      #10

                      Absolutely. 128 MB is hardly sufficient even for VS6. What OS are you using? Tomasz Sowinski -- http://www.shooltz.com

                      T 1 Reply Last reply
                      0
                      • A Andrew Peace

                        You ran Win2k Server on a laptop :omg:? I found it okay on my old 35mhz k6-2 (upgraded since, however). [edit] I mean my 350mhz k6-2. Now that would've been sloooowwwwww :D. -- Andrew.

                        C Offline
                        C Offline
                        Chris Maunder
                        wrote on last edited by
                        #11

                        I wrote CodeProject on this crusty old thing! :D cheers, Chris Maunder

                        1 Reply Last reply
                        0
                        • C CSharpDavid

                          Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

                          O Offline
                          O Offline
                          Oz Solomon
                          wrote on last edited by
                          #12

                          One thing is for sure - VS.NET is slooooooooow at checking dependencies (I was using Beta 2). On my dual Athelon /w 512mb, it took over a minute to check dependencies for a workspace of about 30 projects. X| Imagine waiting that long every time you hit the compile button... -Oz --- Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...

                          1 Reply Last reply
                          0
                          • C CSharpDavid

                            Is everyone else finding that VS.Net runs like a dog on anything less than a 1gig machine. I have just removed it from my computer and put VS6 back on it , screw .NET .:(( What Intel gives, Microsoft will soon take away.

                            R Offline
                            R Offline
                            Russell Morris
                            wrote on last edited by
                            #13

                            Computer: 1.7G P4, 512M RAM I installed VS.NET Beta2 on an IDE drive (UltraATA/66, I think) and load times were tolerable. My brain then turned on, and I uninstalled and reinstalled it on my Ultra160 SCSI drive. Load time is now pretty much instantaneous. Moral of the story - disk access is as much a factor of load time as processor speed and memory size. Since IDE has to utilize CPU cycles to move data around, I'd say that it matters even more on a slower machine when you're loading a behemoth like VS.NET. But, of course, there's no way getting around the fact that VS.NET is monstrous ;) -- Russell Morris "WOW! Chocolate - half price!" - Homer Simpson, while in the land of chocolate.

                            1 Reply Last reply
                            0
                            • T Tomasz Sowinski

                              Absolutely. 128 MB is hardly sufficient even for VS6. What OS are you using? Tomasz Sowinski -- http://www.shooltz.com

                              T Offline
                              T Offline
                              tonyschr
                              wrote on last edited by
                              #14

                              That's your problem. I think the minimum system requirements are actually 160 MB on XP, and a bit lower for other platforms. Go for 256 - 512 MB if you can. --CoolDev :cool:

                              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