|
George wrote:
One-size-fits all simply doesn't work well when it comes to IDEs
After working with it for a good six months now, I've found the IDE to be not as bad as I first thought. (Although, I tend to be writing code by hand rather than using the wizards)
George wrote:
Using the integrated source control will trash the project level changes history by filling it with lots of entries like "Added ~sak5a3bbbd501c3d918.tmp" followed closely by "Deleted ~sak5a3bbbd501c3d918.tmp". If you will carelesly start a build and then try to checkin your files or diff at the same time then you may get a hung IDE at the build end. You can't close the IDE any more as it claim that you ought to close some imaginary popup window.
Not seen that happen. Is this with Visual Sourcesafe integration?
George wrote:
Using the wizard to add message hanlers and virtual overrides will switch the files after each addition so if you want to add more than one it get's a bit tiresome. And on top of that it will inject redundant include line with header name in lover case preceded by "./". That micro-management doesn't seem to serve any real purpose.
Oh yes, one of my biggest problems with the new IDE, that's why I started handcoding a lot of the stuff.
Michael
But you know when the truth is told,
That you can get what you want or you can just get old,
Your're going to kick off before you even get halfway through.
When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
|
|
|
|
|
We recently moved from VC6 to VS.NET 2003 and I think this was a mistake. We only do c++ and MFC development. Although there are some improvements, there are a lot more things that are worse. VS.NET is more crashy, slower and buggy. The UI is sluggish and badly designed - the resouce editor is really awful.
|
|
|
|
|
Anonymous wrote:
VS.NET is more crashy, slower and buggy.
I've not had any major problems with VS.NET 2003. 2002 was a bitch, but the current version works a lot better.
Anonymous wrote:
The UI is sluggish and badly designed
After you've used it for a while, you find it grows on you. I certainly feel more productive using it.
Anonymous wrote:
the resouce editor is really awful.
I don't use it much. Most of my legacy code I maintain, doesn't need much in the way of UI changes. For my C# work, my apps build their ui from an XML file (which I currently handcode). The resource editor is probably easier to grips with, if you've done any VB6 programming
Michael
But you know when the truth is told,
That you can get what you want or you can just get old,
Your're going to kick off before you even get halfway through.
When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
|
|
|
|
|
>the resouce editor is really awful.
Well said. The resource editor in VS6 is much better - copying resources from other .RC files for example. Plus, the only crashes I have had in VS.2003 have been when resource editing. There is also a highly annoying bug which means some resource elements end up as numeric IDs instead of the #define - e.g.:
"&Open", 31234
instead of:
"&Open", ID_FILE_OPEN
The real problem with this is when you try to use the new ClassWizard to add a WM_COMMAND handler, you see a list of bloody numbers instead of readable commands! Aaaarrrggghhh!
The Rob Blog
|
|
|
|
|
Robert Edward Caldecott wrote:
There is also a highly annoying bug which means some resource elements end up as numeric IDs instead of the #define - e.g.:
"&Open", 31234
instead of:
"&Open", ID_FILE_OPEN
That is one of the most annoying bugs that I have found in the program. I end up changing the IDs back to the #define name and VC++.NET ends up sooner or later, changing it back to the number. Weird stuff.
Talk about something that needs to be fixed!
BNEACETP
|
|
|
|
|
I have another one.
Try
String *strNet = S"llll";<br />
CString strATL;<br />
strATL = strNet;
<br />
String *strNet = S"llll";<br />
CString strATL = strNet;
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
String *strNet = S"llll";
CString strATL;
strATL = strNet; //This will give compile error on my VS.NET 2002
String *strNet = S"llll";
CString strATL = strNet; //this works, weird
That is some weird stuff...
BNEACETP
|
|
|
|
|
Anonymous wrote:
We only do c++ and MFC development
C++ projects that do not use MFC benefit greatly from VS.NET 2003 IMO. This is mainly down to the compiler rather than the UI. Everything is better from standards support right down to error messages.
Anonymous wrote:
VS.NET is more crashy, slower and buggy. The UI is sluggish and badly designed
I am another person who finds it better. The main improvement UI wise is the text editor and the debugger. However, this is only because my comp can run it at a decent speed. It must be horrible on an older comp.
I can honestly say I have not seen crashes. But I have seen the odd 100% cpu use (only working on asp.net projects). I would guess I don't see many problems because I do not use the resource editor.
|
|
|
|
|
Mazy
No sig. available now.
|
|
|
|
|
Sorry to disagree. VC6 is not a stable version. I used to use bookmarks and brief-emulation, which resulted in daily crashes. Intellisense surprisingly popups, sometimes. The class-tree frequently gets corrupted. The resource editor, well it was not so bad if you haven’t seen the resource handling in Visual Studio.Net. Although, a nice feature I miss is debug – apply code changes.
|
|
|
|
|
Leifen wrote:
The class-tree frequently gets corrupted
Yep. It was unusable with namespaces and folders in VC6. It would just forget them In VS2003 I have not found a single problem after I set that option that prevents it from jumping around. It took em a while, but I have to say, at last, MS got it right. For what I do anyway 
|
|
|
|
|
I have mixed feelings about new IDE (it is too slow and unresponsive sometimes), but the fact that we have a decent Standard Library would be enough for me to switch, not to mention compiler improvements (VC 7.1 is 98% ISO compliant) and ATL Server.
|
|
|
|
|
And I really hate the attached MSDN.
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
Anonymous wrote:
the resouce editor is really awful.
Resources are so '90's. Most (if not all) of our new apps now use XML based resources and generate the UI on the fly. Sure, it was a big hit to code that all up the first time, but it's working quite well now.
As for VS.NET - we are still on VS.NET 2002, and it's been a mixed bag. I think I do like the UI better, although it took a while. The compiler is mostly better. There are some annoying... how shall we say, issues, in the new MFC, but we hardly ever use MFC anymore these days. Unicode support is much better in VS.NET than in VC6. VC6 seemed to be more stable, though, as there are often little annoying things that come up from time to time that can drive me crazy.
"I'd be up a piece if I hadn't swallowed my bishop." Mr. Ed, playing chess
|
|
|
|
|
We have mixed sites with both frameworks and classic therefore I still manage and edit my files in VS6 because I can. On the other hand I use VS 7(2002) for desktop applications. VS7 is too napoleonic to use for web site development. I prefer to create my classes and code behind in a different folder and I don't er won't use the designer so it is a waste of my energy and money.
Pam
Some days the Dragon wins!!
Pamela Reinskou
VersusLaw Inc.
|
|
|
|
|
For those who chose the "Non-MS" option, what do you use?
~Nitron.
ññòòïðïðB A start
|
|
|
|
|
IntelliJ and Sun J2EE/J2SE.
--
I am perpetual, I keep the country clean.
|
|
|
|
|
IntelliJ, nice
Sonork 100.41263:Anthony_Yio
|
|
|
|
|
We're using Universe for both database and back-end processing.
"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.
Support Bone
It's a weird Life
|
|
|
|
|
Nick Seng wrote:
We're using Universe for both database and back-end processing.
My sympathies
Michael
But you know when the truth is told,
That you can get what you want or you can just get old,
Your're going to kick off before you even get halfway through.
When will you realise... Vienna waits for you? - "The Stranger," Billy Joel
|
|
|
|
|
My thanks.
"if you vote me down, I shall become more powerful than you can possibly imagine" - Michael P. Butler.
Support Bone
It's a weird Life
|
|
|
|
|
|
Maxwell Chen wrote:
Linux
Oh man, c'mon; think of the penguins!
~Nitron.
ññòòïðïðB A start
|
|
|
|
|
That's interesting. And you still find this site of great use?
John
|
|
|
|
|
There are two teams in our company, Windows and Linux.
I belong to Windows team.
Maxwell Chen
|
|
|
|