|
And me makes three
James
At Jethro Tull's August 28, 2003 concert Ian Anderson mentioned that the group would be performing a medley of title tracks. The songs were "Songs from the Wood", "Too Old to Rock and Roll; Too Young to Die"; and from the Heavy Horses album, "Stairway to Heaven".
|
|
|
|
|
Of course, the IDE I used before this was VB6, so it's probably not a good comparison.
Yeah, VB6 was so bad and I don't think there was any need for it. It seemed to have no new features and all the bugs from VB5.
|
|
|
|
|
I'm another "Very Satisfied"
Having used both VB6 and VC6 IDE's a ton, VS.NET 2003 is by far the best IDE I've ever used. It has all of the cool features they tried to do in the Visual InterDev environment but didn't quite get right.
My one major complaint with VS.NET 2003 is this:
Why oh why didn't they replace Visual SourceSafe!?!?!
don
|
|
|
|
|
FYI, this[^] is a project that's aimed at creating a Windows-based source control system. It started out here on CodeProject, but it later moved off of there. My Fluid UI Toolkit project shares forums with it.
"Blessed are the peacemakers, for they shall be called sons of God." - Jesus
"You must be the change you wish to see in the world." - Mahatma Gandhi
|
|
|
|
|
Yep, very satisfied! 
|
|
|
|
|
|
You have my sympathies
|
|
|
|
|
the dreaded class view!
In a larger project, with *lots* of stuff in the class view, the updates of this view is really annoying. Edit anything in a .h-file and you'll notice it. I notice it on a 1.2 Ghz AMD with 768 MB RAM in it. It locks up the entire editor for 0.1 seconds or so. It may sound like a minor issue, but when you edit a .h file and it keeps refreshing the class view every 1-2 second, it becomes a problem!
The only workaround I know of so far is to switch to the solution/file view. That one isn't refreshed like the classview. Even if I'd buy a twice as fast computer, the editor lock would still be noticable and very annoying.
As my larger projects are only in C++, I don't know if this problem occurs with other languages as well. Has anyone else noticed this?
Another minor issue: When you create folders in the class view to logically group classes, wouldn't it be nice if you could drag items a bit faster in the class view? When you need to drag something past the end or top of the view, the scrolling is way too slow IMHO.
(Desperately hoping that someone @ microsoft reads this and fixes it - Nick, are you there?  )
--
Frivolous Theorem of Arithmetic: Almost all natural numbers are very, very, very large.
|
|
|
|
|
Try on a Win 9x machine and everything is OK. This is a standard prblem of Windows NT+
|
|
|
|
|
We are stuck using VS.NET 2002, v1. Apparently the bugs found in in this version have not been fixed in 2003 (resource editor wackiness, in particular), and this would be our only reason to upgrade; so we'll be using the 2002 version for the forseeable future.
If MS would provide bug fixes, we might be more inclined to keep up with these upgrades.
The delivery of the promised service pack for 2002 would also help restore our faith in MS's ability to deliver quality development tools. Right now it seems their only motivation is support for their technology du jour (.NET).
|
|
|
|
|
That's right. VS .net 2002 Is really a great dev-tool, but some bugs are really sucking (intelli-sense crashes weekly).
Give me a service pack and i'm happy for future!
But when i see Borland C++ Builder? Yeah, VS. net is really bugfree *g*.
Excuse my english!
|
|
|
|
|
Have not got my free upgrade in my academic licensing agreement yet...
John
|
|
|
|
|
I am using VS.2003 primarily because ATL7 is really very good indeed, and the new C++ compiler is closer to what you'd expect nowadays. However, as an IDE it can be very frustrating to work with - I don't like the new look and feel very much - the sliding toolbars/panes require my hand to be on the mouse more than in VS6 and, quite frankly, I wish they had left the UI alone.
There are numerous bugs - and they are annoying enough to slow me down and make me want to throw my PC out the window. For example, using a solution containing projects that share filenames (MainFrm.cpp/MainFrm.h is a classic - I have projects where adding a Windows message handler will add the prototype to the correct MainFrm.h and the function to a MainFrm.cpp from another project. Marvellous). There is also a resource editing bug that means my .rc file can end up having the #defined symbols (e.g. ID_FILE_OPEN) replaced with the numeric IDs instead. How useful. Especially as when you then hit Alt+Enter to display the dubious new "ClassWizard" in order to add a WM_COMMAND handler and you see a list of numeric IDs instead of the definition. I am having to edit my .rc files by hand on a daily basis which is wasting my time.
I also get regular crashes - again often when resource editing - something that I am not used to quite frankly as VS6 was 100% reliable (and was from day one apart from the odd MFC-ism).
MFC7 also has it's problems - try getting an MFC7 app to run on Win95 - it requires a DLL (OLEACC) that isn't present. Yeh, there's a workaround, but even so...
So on the one hand I have got a new compiler that I like and ATL7 has been enhanced no end and on the other the development environment has been messed with to the extent that I end up ranting at the screen on a daily basis.
Here's hoping for a service pack soon!
The Rob Blog
|
|
|
|
|
Robert Edward Caldecott wrote:
I also get regular crashes - again often when resource editing - something that I am not used to quite frankly as VS6 was 100% reliable (and was from day one apart from the odd MFC-ism).
Doh. VS6? 100% reliable? Every tried to open a bunch of bitmap files at once? Or edit a checked in resource file (bmp, html, etc)? Edit a HTML resource, compile, run and then - well, the HTML file is readonly in the editor for no reason. And quite a few more resource editor bugs come into my mind.
Not that VS.net would be any better here...
As you already mentioned, ATL and compiler are something to go for, but the rest just sucks. Ever tried to use both on VS6 ? 
Finally moved to Brazil
|
|
|
|
|
I couldn't get to like the Wizards and Add-Ins in VS6 anyway and I've been coding C# quite a long time now. I don't think I've been more productive ever before. Ok, there are some flaws and sometimes anoying slow, but it does quite well overall.
Dynamic Help is actually the most useless feature ever.
|
|
|
|
|
LangAl wrote:
Dynamic Help is actually the most useless feature ever.
I agree (at least, in VS.NET 2002.) The help in VS 6 was much better than it is now.
If your nose runs and your feet smell, then you're built upside down.
|
|
|
|
|
Well, at least they're consistent...
every new version of Visual C++ the help system seems to get worse. VC4 was the best, then they really made it sh*tty by introducing HTML help and making it much slower.
|
|
|
|
|
I also like the new IDE. The problem is MSDN. I can't find anything anymore without using Index or Search.
Dynamic Help is nice, though. At least for .NET applications, for native C++ I usually turn it off.
|
|
|
|
|
Yep, but navigating through MSDN's been foul from the start. IMHO it's just more content you struggle to find now...
|
|
|
|
|
The only thing I like less than dynamic help is this[^]. Dynamic help slows the IDE to a crawl as the stupid thing tries to find help topics for everything.
Software Zen: delete this;
|
|
|
|
|
I am a VS.NET user  however, i do enjoy seing Don Box coding away on his emacs during his appresentations and seminars.... ughmmm...however i am too lazy to go back and remember all short-cuts, without short cuts you're can not really code in emacs...can you? 
Cheers,
Erick
|
|
|
|
|
Emacs is nice. I can use borth Emacs and VS.NET. But weird things happen when you use VS.NET at work and Emacs at home. CTRL+Z in Emacs minimizes the window, and CTRL+S starts an incremental search in Emacs. I guess I could reconfigure all that, but I'm too lazy. 
--
Frivolous Theorem of Arithmetic: Almost all natural numbers are very, very, very large.
|
|
|
|
|
I haven't really started using it yet, but so far it looks overall like an improvement.
I'll just make one comment:
When will MS cotton on that ALL dialog boxes should be resizable?
I mean we still have the project properties dialog with 1 inch wide edit boxes containing text of a 100 characters (in the case of my project)
|
|
|
|
|
I'll agree with you, though after replacing "MS" with "All Windows Developers"...
Seriously, WTF?
Shog9
I returned and saw under the sun,
that the race is not to the swift,
nor the battle to the strong...
|
|
|
|
|
The oh-so-popular current slogan says it all actually. In the ironic sort of way 
VS.NET gives less of everything. The usefull features from VS60 disappeared, the old addins won't work any more. On top of that it's much slower giving less time to do the actual work.
It doesn't accept the drag-and-drop of it's own project files telling the user politely to use the Open menu instead.
The code wizards are all other the place and often misleading, swapping the opened document windows forcing to search for the resource view again and again.
The help system got screwed even more this time (E.g. why would I want my MSDN favorites mixed up with other internet ones?).
The thing "upgrades" the VS.NET 2002 files into new format making it really hard to upgrade IDE smoothly.
The integration with Source Safe has quite a few issues on it's own, sometimes leading to hanging situation when it wrongly thinks there is a modal dialog displayed.
It crashes every now and then for no apparent reason.
One of the most annoying "features" is the micro-management of the code. The adding of the include statemnt with the ".\" preceding the include file name really ticks me off. The second-guessing of the HTML files content is actually dangerous as it can destroy a lot of the file if you're not paying attention. On some occasions the in-memory file image will go out of synch with the disk version generating bogus compilation errors. Only after a while one can see that IDE has inserted a duplicate of the code from another place in the same file...
And why can't I define my own output window backgound color?
On the good side I can only mention the line numbers and outlining display.
Probably the only thing that makes the work with VS.NET 2003 IDE possible at all is the Visual Assist installed. Without that VS.NET usability for developing code is close to the one of Notepad.
<center> </center>
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
