|
Ok. With this one it'll be enough ... I'lll order it 
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
Use 2005 Exclusivly now.
Running on 3.4 ghz P4, 550J Prescot with 2 Gigs of memory.
It still slows every once in awhile, all MS products are resource hogs.
Matthew Hazlett
Sometimes I miss the simpler DOS days of Borland Turbo Pascal (but not very often).
|
|
|
|
|
I had that problem too, changed my computer by adding more memory.
but 1 GB isn't much of a problem, I even run VS2005 on my notebook a Pentium M 1.7 with 512MB memory.
WM.
What about weapons of mass-construction?
|
|
|
|
|
On this Pentium D 950 with 4GB RAM and Windows XP x64, VS2005 runs as responsive as Notepad. 
The only problem is you get so used to it being so responsive that when you are forced to use it on a less powerful machine then all the little performance annoyances drive you mad.
|
|
|
|
|
Nice box !!!  I'd like to have one like this, even though I get disappointed when using other computers.
... she said you are the perfect stranger she said baby let's keep it like this... Dire Straits
|
|
|
|
|
Michael P Butler wrote: No more messing about with the older technologies. .NET 2 has too many advantages to not use it for all development going forward.
Don't forget the bugs in the framework and VS2005 this is a good reason to keep using the VS2003 and .NET 1.1
I love 2.0 but I must wait to the SP1 to use it at work.
Cheers
|
|
|
|
|
Marcos Meli wrote: Don't forget the bugs in the framework and VS2005 this is a good reason to keep using the VS2003 and .NET 1.1
I haven't found anything that break anything I need. Okay, VS2005 can be a little unstable at times but I've learnt to work round its quirks.
The excellent Enterprise Library 2.0, Smart Client Software Factory and the Composite UI Application block more than make up for the shortcomings of VS2005 pre-servicepack.
|
|
|
|
|
Michael:
We have a lot of trouble with inherited win forms, some thread code, for example some days ago I found in a blog that there is a bug in the string.IsEmptyOrNull of the .NET 2.0. Do you think that this is not buggy. BTW I love .NET 2.0, I only want and need the SP1 !!! In my dialy work we don't need atlas, WPF, WCF .NET 3.0 at all. We only need the SP1 to release our bussines app in the company we are still using .NET 1.1.
Some time ago when we release the ported version, time by time the application hang ups and shows an screen with an error and a "SEND TO MICROSOFT" button... WTF !!! send to MS ?? is our program !!, we are using Application.ThreadException why this append ?. In the previous version all the errors pass for the seted handler. We can't accept it at all.
Our application has more than 100.000 lines of code we can debug it again and found that there is a problem in the framework.
Best Regards
Marcos
|
|
|
|
|
I couldn't agree more !!!
generics, anonymous methods, refreshed remoting and ADO.NET are truly useful, those are not just cheap slogans.
Dotnet 3.0 will be even more powerfull. I've seen demo version and can't wait to see final one.
Felin
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
