VS2005 makes me mad
-
Damn it! It is sooo slow! 8( I am testing my application in NUnit. I do "attach to process" to do some debugging. This action took me about 5 seconds in VS2003. Now I can read all postings in this forum before VS2005 reply sthm to my action. I have 1 GB of memory, Pentium 4 3.00 Hz with HT - is this configuration too bad for VS2005?
-
Damn it! It is sooo slow! 8( I am testing my application in NUnit. I do "attach to process" to do some debugging. This action took me about 5 seconds in VS2003. Now I can read all postings in this forum before VS2005 reply sthm to my action. I have 1 GB of memory, Pentium 4 3.00 Hz with HT - is this configuration too bad for VS2005?
I find running NUnit under debug to be exceptionally slow in both versions. Oddly enough, attaching to the process is OK...the long delays (typically 30s or so) start when I press the "Run Test" button in the NUnit GUI. :confused: I think it's a Framework issue, possibly caused by the heavy use of reflection within the NUnit libraries. I've certainly not seen the same issues with native processes under debug in either IDE.
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
I find running NUnit under debug to be exceptionally slow in both versions. Oddly enough, attaching to the process is OK...the long delays (typically 30s or so) start when I press the "Run Test" button in the NUnit GUI. :confused: I think it's a Framework issue, possibly caused by the heavy use of reflection within the NUnit libraries. I've certainly not seen the same issues with native processes under debug in either IDE.
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
You are absolutely right. When I press Run Test I can go and make myself tea... So i go...
-
I find running NUnit under debug to be exceptionally slow in both versions. Oddly enough, attaching to the process is OK...the long delays (typically 30s or so) start when I press the "Run Test" button in the NUnit GUI. :confused: I think it's a Framework issue, possibly caused by the heavy use of reflection within the NUnit libraries. I've certainly not seen the same issues with native processes under debug in either IDE.
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
Look, if you using NUnit, maybe you could help me? 8) I have problems with bindings in my tests. It looks like controls are filled with values from datasource only when they are visible. So when I need to check some control for data in it, I am forced to make form visible for a while. I think that this is a not very good idea. Maybe you had same problems? If you did, could you please tell how you solved it. 8)
-
Damn it! It is sooo slow! 8( I am testing my application in NUnit. I do "attach to process" to do some debugging. This action took me about 5 seconds in VS2003. Now I can read all postings in this forum before VS2005 reply sthm to my action. I have 1 GB of memory, Pentium 4 3.00 Hz with HT - is this configuration too bad for VS2005?
springjazzy wrote:
3.00 Hz
There's your problem. You need to install a 'G' :cool: 2GB can't hurt, and what disks you have? Check Task manager / performance Monitor if memory is exhausted, and if VS2005 is wapping like mad.
springjazzy wrote:
I have 1 GB of memory, Pentium 4 3.00 [G]Hz with HT
I've been running VS2005 on a configuration like that, and while it doesn't rock, it at least rolls.
Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Linkify!|Fold With Us! -
You are absolutely right. When I press Run Test I can go and make myself tea... So i go...
I'm glad it's just not me! At first I thought it might be an unintended consequence of the odd way we use NUnit (for testing native C++ code, no less! *), but I've since had the same behaviour confirmed to me by a .NET developer I know who is seeing the same thing with a third party component. I guess managed debuggers still have some way to go to mature. :doh: * My current pet project is a native Visual Studio automation library that can handle everything from VS6 and eVC4 up to VS2005. The unit tests involve automating five different versions of Visual Studio running exactly the same test code. No conditional compilation, no checking which interface is returned...it just works. :cool: When it's a bit more advanced and we've used it in anger, there's definitely an article in there somewhere... :)
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
Look, if you using NUnit, maybe you could help me? 8) I have problems with bindings in my tests. It looks like controls are filled with values from datasource only when they are visible. So when I need to check some control for data in it, I am forced to make form visible for a while. I think that this is a not very good idea. Maybe you had same problems? If you did, could you please tell how you solved it. 8)
We use NUnit for testing native Visual Studio extensibility code, so forms and datasources are things we don't use. Why don't you try asking in the TDD Group instead[^]?
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
springjazzy wrote:
3.00 Hz
There's your problem. You need to install a 'G' :cool: 2GB can't hurt, and what disks you have? Check Task manager / performance Monitor if memory is exhausted, and if VS2005 is wapping like mad.
springjazzy wrote:
I have 1 GB of memory, Pentium 4 3.00 [G]Hz with HT
I've been running VS2005 on a configuration like that, and while it doesn't rock, it at least rolls.
Developers, Developers, Developers, Developers, Developers, Developers, Velopers, Develprs, Developers!
We are a big screwed up dysfunctional psychotic happy family - some more screwed up, others more happy, but everybody's psychotic joint venture definition of CP
Linkify!|Fold With Us!At work I have a workstation that has exactly that configuration and runs pretty smooth. It does get slow however if I try to add a reference to my project for the first time. I think he's better off poking his boss for a dual cpu workstation (core 2 duo or something like that) and 2G+ memory.
WM. What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
-
At work I have a workstation that has exactly that configuration and runs pretty smooth. It does get slow however if I try to add a reference to my project for the first time. I think he's better off poking his boss for a dual cpu workstation (core 2 duo or something like that) and 2G+ memory.
WM. What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
Yes, I'm already thinking about buying supercomputer to work with VS2005... I wonder if I could turn off some feats in VS2005... I hope it wouldn't turn into notepad after that... 8)
-
I'm glad it's just not me! At first I thought it might be an unintended consequence of the odd way we use NUnit (for testing native C++ code, no less! *), but I've since had the same behaviour confirmed to me by a .NET developer I know who is seeing the same thing with a third party component. I guess managed debuggers still have some way to go to mature. :doh: * My current pet project is a native Visual Studio automation library that can handle everything from VS6 and eVC4 up to VS2005. The unit tests involve automating five different versions of Visual Studio running exactly the same test code. No conditional compilation, no checking which interface is returned...it just works. :cool: When it's a bit more advanced and we've used it in anger, there's definitely an article in there somewhere... :)
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
Did you enjoy HotFuzz? :-D
-
At work I have a workstation that has exactly that configuration and runs pretty smooth. It does get slow however if I try to add a reference to my project for the first time. I think he's better off poking his boss for a dual cpu workstation (core 2 duo or something like that) and 2G+ memory.
WM. What about weapons of mass-construction? "What? Its an Apple MacBook Pro. They are sexy!" - Paul Watson
-
Did you enjoy HotFuzz? :-D
Very much so. I've not laughed so much in ages. :laugh: Highly recommended. :-D
Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
Yes, I'm already thinking about buying supercomputer to work with VS2005... I wonder if I could turn off some feats in VS2005... I hope it wouldn't turn into notepad after that... 8)
-
Damn it! It is sooo slow! 8( I am testing my application in NUnit. I do "attach to process" to do some debugging. This action took me about 5 seconds in VS2003. Now I can read all postings in this forum before VS2005 reply sthm to my action. I have 1 GB of memory, Pentium 4 3.00 Hz with HT - is this configuration too bad for VS2005?
-
Damn it! It is sooo slow! 8( I am testing my application in NUnit. I do "attach to process" to do some debugging. This action took me about 5 seconds in VS2003. Now I can read all postings in this forum before VS2005 reply sthm to my action. I have 1 GB of memory, Pentium 4 3.00 Hz with HT - is this configuration too bad for VS2005?
springjazzy wrote:
I have 1 GB of memory, Pentium 4 3.00 Hz with HT
That's my laptop configuration (except for the 3 hz that has already been mentioned). VS2005 rocks. Well, it rocks after I wiped the hard disk, re-installed the OS and only the stuff I need for dev. Marc
People are just notoriously impossible. --DavidCrow
There's NO excuse for not commenting your code. -- John Simmons / outlaw programmer
People who say that they will refactor their code later to make it "good" don't understand refactoring, nor the art and craft of programming. -- Josh Smith -
Damn it! It is sooo slow! 8( I am testing my application in NUnit. I do "attach to process" to do some debugging. This action took me about 5 seconds in VS2003. Now I can read all postings in this forum before VS2005 reply sthm to my action. I have 1 GB of memory, Pentium 4 3.00 Hz with HT - is this configuration too bad for VS2005?
IMO SP1 speeds some things up, however installing SP1 isn't too spritely either ;)
Ant. I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain) -
WillemM wrote:
he's better off poking his boss
I'd becareful on that one, this can be misinterpreted on many levels :)
We made the buttons on the screen look so good you'll want to lick them. Steve Jobs