|
I don't agree - it's grown on me rather quickly. It is less stable (not surprising for such a radical change) and does require more screen real estate than previously - but then so did VC 4.0. Ever use VC 1.52?
The one thing I do miss is WndTabs[^]...VS.NET's tabbed interface is nowhere near as good.
As an add-in author I can also tell you that the VS.NET extensibility model is a huge improvement on that in VS6. 
Anna ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
www.annasplace.me.uk
"Be yourself - not what others think you should be"
- Marcia Graesch
Trouble with resource IDs? Try the Resource ID Organiser Add-In for Visual C++
|
|
|
|
|
Anna-Jayne Metcalfe wrote:
he one thing I do miss is WndTabs[^]...VS.NET's tabbed interface is nowhere near as good.
Maybe you'd like to check an add-in at www.smarthelp.net. One of its features allows you to have your tabs rendered similarly to WndTabs's in VS6.
As an add-in author I can also tell you that the VS.NET extensibility model is a huge improvement on that in VS6.
It's incredibly buggy and undocumented.
- Goran.
|
|
|
|
|
Goran Mitrovic wrote:
Maybe you'd like to check an add-in at www.smarthelp.net. One of its features allows you to have your tabs rendered similarly to WndTabs's in VS6.
I've tried SmartHelp, but I just didn't get on with it I'm afraid...it just didn't give the flexibility I was used to in the registered version of WndTabs. My personal favourite is right clicking on a grouped tab and closing all the others except that one, closely followed by "Make Read-Write/Make Read-Only")
Goran Mitrovic wrote:
It's incredibly buggy and undocumented.
Sadly, that's normal for the COM interface on Microsoft products. VS6 and SourceSafe are no different in that regard. 
Anna
www.annasplace.me.uk
"Be yourself - not what others think you should be"
- Marcia Graesch
Trouble with resource IDs? Try the Resource ID Organiser Add-In for Visual C++
|
|
|
|
|
Speed and stability is the number one choice, I think mainly because of the lack of speed and stability in VS.NET. Funny how priorities are re-ordered when problems occur.
Good poll btw
Paul Watson
Bluegrass
Cape Town, South Africa
Roger Wright wrote:
Using a feather is kinky; using the whole chicken is perverted!
|
|
|
|
|
Paul Watson wrote:
lack of speed and stability in VS.NET
FWIW I've been using VS.NET 2003 beta 2 and I can't remember the last time it crashed. Speed is also a non-issue (admittedly I've got a 1.8GHz/512MB machine)
cheers,
Chris Maunder
|
|
|
|
|
Chris Maunder wrote:
FWIW I've been using VS.NET 2003 beta 2 and I can't remember the last time it crashed.
That is wonderful to hear. I have barely managed to get my team onto VS.NET 1, so 2003 is going to have to wait a bit.
Chris Maunder wrote:
Speed is also a non-issue (admittedly I've got a 1.8GHz/512MB machine)
Thing is, other apps are fine on my machine, but VS.NET is a touch slow. Some of the other apps have a much better reason (graphic apps) for being slow, something VS.NET does not. Still, the problems are nothing to write home about.
Paul Watson
Bluegrass
Cape Town, South Africa
Roger Wright wrote:
Using a feather is kinky; using the whole chicken is perverted!
|
|
|
|
|
Paul Watson wrote:
lack of speed and stability in VS.NET.
Funny i've been using VS.Net for the last year or so and it hasn't crashed on me unless i overload my system too much.
I am surprised that people feel VS6 was more better.
May the Source be with you
Sonork ID 100.9997 sijinjoseph
|
|
|
|
|
VS.NET rarely crashes on me, but when compiling I often get "internal compiler error" problems, and have to rebuild everything for them to go away. 
Here's to hoping that VS 2003 is better in that regard...
You can pick your friends, and you can pick your nose, but you can't pick your friend's nose.
|
|
|
|
|
Sijin wrote:
Funny i've been using VS.Net for the last year or so and it hasn't crashed on me unless i overload my system too much.
I don't know what you mean by "overload your system", but the IDE should never crash, overload or otherwise.
I'm sorry to say that if the IDE only crashes on me once a day, I count my blessings. 5-10 times a day is more realistic...
Sijin wrote:
I am surprised that people feel VS6 was more better.
Sometimes simpler is better. But really, it's a matter of taste. So far as the VS7 IDE goes - if I have a chance, I stick with the VC6 IDE. Maybe VS2003 will be somewhat better, though from what I saw in Beta 2, it's not that big of an improvement.
-Oz
---
Grab WndTabs from http://www.wndtabs.com to make your VC++ experience that much more comfortable...
|
|
|
|
|
Paul Watson wrote:
I think mainly because of the lack of speed and stability in VS.NET.
To be honest, i'd pick those above all else even though i still use VS6 much more heavily than VS.NET. I have ugly memories of running VS6 on a 64MB 500MHz PC not too long ago... Crashes were just occasional enough to piss me off without making it unusable, while the speed... ugh... when moving the cursor from one function to another hangs the IDE for better than 5secs, it gets hugely frustrating in a hurry.
---
Shog9
The siren sings a lonely song - of all the wants and hungers
The lust of love a brute desire - the ledge of life goes under
|
|
|
|
|
I thought my vote may b the first vote for this survey. But before me submitting the answer... someone has submitted the voting.....
I was born intelligent
Education ruined me!.
|
|
|
|
|
;
jason
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
