VS2005 - First impressions
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
Alex Orovetskiy wrote:
- it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process
Yep, same here. I've found it slow - both the install and the app. Slower than 2003, that is, which was slower than VC6. So there's a trend there.
Alex Orovetskiy wrote:
- IntelliSense seem to be working like it should be now
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Alex Orovetskiy wrote:
- They finally fixed Chineese being the default language when creating new MFC project
Huh? I've never had that one.
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
Alex Orovetskiy wrote:
- it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process
I don't have any speed problems other than startup.
Alex Orovetskiy wrote:
- the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now
That is a complaint of mine. We're programmers. We don't need eye-candy. We need a tool that works, and works fast.
Alex Orovetskiy wrote:
- Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings.
Yup. Converting VC6 projects has been fairly painless as well. ------- sig starts "I've heard some drivers saying, 'We're going too fast here...'. If you're not here to race, go the hell home - don't come here and grumble about going too fast. Why don't you tie a kerosene rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt "...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
Alex Orovetskiy wrote:
MSDN...In short the design sucks. I prefered the one in Jan 2005
I simply hate MSDN Libray 2005! It's slow, I cannot find any interesting info, and the search filters don't work! When you select as languages C# and VB, the library offers results for JScript!!! Is this normal??? ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA] - eMule Server .NET
-
Alex Orovetskiy wrote:
- it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process
Yep, same here. I've found it slow - both the install and the app. Slower than 2003, that is, which was slower than VC6. So there's a trend there.
Alex Orovetskiy wrote:
- IntelliSense seem to be working like it should be now
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Alex Orovetskiy wrote:
- They finally fixed Chineese being the default language when creating new MFC project
Huh? I've never had that one.
Nishant Sivakumar wrote:
So there's a trend there.
Like with every M$ product *sigh*
Nishant Sivakumar wrote:
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
I also do C++\MFC only but this time it at least shows the right stuff. Mostly.
Nishant Sivakumar wrote:
Huh? I've never had that one.
I think there was even a workaround here on CP for that problem. So it is not my imagination :) -------------------------------- Human stupidity is infinite.
-
Alex Orovetskiy wrote:
MSDN...In short the design sucks. I prefered the one in Jan 2005
I simply hate MSDN Libray 2005! It's slow, I cannot find any interesting info, and the search filters don't work! When you select as languages C# and VB, the library offers results for JScript!!! Is this normal??? ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA] - eMule Server .NET
Dario Solera wrote:
Is this normal???
Probably not :) But I need VC++ and for it Jan 2005 works fine. Although I admit that the new one (Dec 2005 or what ?) is faster apart from VS2005 itself... -------------------------------- Human stupidity is infinite.
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
Alex Orovetskiy wrote:
Converting VS2003 project to VS2005 was smooth and easy
After finding some speed issues and other funnies, I wish there was a VS2005 to VS2003 project converter. X|
Alex Orovetskiy wrote:
I don't think fancy effects are all that useful for programmers
amen Cheers, Simon > blog:: brokenkeyboards > my opinion of VS05 :: here > CV :: PDF > article :: SVG animation
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
Alex Orovetskiy wrote:
MSDN...In short the design sucks. I prefered the one in Jan 2005
Me too. I find it infuriatingly difficult to find the information I want in those new design pages. What the hell were they thinking?!
Ðavid Wulff Audioscrobbler :: flickr Die Freiheit spielt auf allen Geigen (video)
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
-
I think that code snippets were present in 2k3 too. -------------------------------- Human stupidity is infinite.
-
There are definite performance improvements in the .NET 2.0 runtime, and some performance improvements in the BCL, and then there are some areas in the BCL where higher-level or deprecated classes are a little slower. Despite the latter, I've found it to be faster overall.
-
Yeap, yet another VS2005 thread. So here it goes: 1) it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process 2) the design is quite nice but I don't think fancy effects are all that useful for programmers when they make VS2005 even slower that it is now 3) IntelliSense seem to be working like it should be now 4) That idiotic bug where I cannot modify menu resource ID from resource editor is still there 5) They finally fixed Chineese being the default language when creating new MFC project 6) We now have a bit of code highlighting. How nice. Now where's my Visual Assist ? 7) The debug process became easier it seems. I haven't really tried but now working code has green bar on the left, unchecked - yellow and non-working - red. It seems. Like I've said I'm running a test app. 8) Code Definition and Call Browser seem to be nice 9) MSDN...In short the design sucks. I prefered the one in Jan 2005 10) Converting VS2003 project to VS2005 was smooth and easy. And it compiled mainly nice apart of some warnings. First impression: it is nice but not worth moving from 2003. I've yet to work using it a bit more to form my overall impression though. -------------------------------- Human stupidity is infinite.
Alex Orovetskiy wrote:
- That idiotic bug where I cannot modify menu resource ID from resource editor is still there
Oh man, that SUCKS. It is the one issue that I'd hoped to see fixed - that bug has existed since VS 2003 was released. Sigh. Why on earth could they not of fixed it? Grrrrrrrrrr.
The Rob Blog
Google Talk: robert.caldecott -
Alex Orovetskiy wrote:
- it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process
Yep, same here. I've found it slow - both the install and the app. Slower than 2003, that is, which was slower than VC6. So there's a trend there.
Alex Orovetskiy wrote:
- IntelliSense seem to be working like it should be now
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Alex Orovetskiy wrote:
- They finally fixed Chineese being the default language when creating new MFC project
Huh? I've never had that one.
Nishant Sivakumar wrote:
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Please check the following link regarding the memory leak in iostream and the possible workaround ... http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=e08bd793-3fef-40ff-adda-ed313e0eafcc[^] Thanks, Madhu.
-
Alex Orovetskiy wrote:
- it is slow. No, it is frigging slow. Starting from the setup and ending with configuration process
Yep, same here. I've found it slow - both the install and the app. Slower than 2003, that is, which was slower than VC6. So there's a trend there.
Alex Orovetskiy wrote:
- IntelliSense seem to be working like it should be now
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Alex Orovetskiy wrote:
- They finally fixed Chineese being the default language when creating new MFC project
Huh? I've never had that one.
Nishant Sivakumar wrote:
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Isn't that why Visual Assist exists? Stuart Dootson 'Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p'
-
Nishant Sivakumar wrote:
Not for me. I only do VC++ projects, maybe C++ intellisense is not so well implemented.
Please check the following link regarding the memory leak in iostream and the possible workaround ... http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=e08bd793-3fef-40ff-adda-ed313e0eafcc[^] Thanks, Madhu.
Oh yeh, I forgot about this terrible leak! And I use wstringstream everywhere. Nasty - and the fix is a lot of effort. You know, after reading these posts the last few days, I am going to wait until a decent Service Pack before I start using VS 2005. It doesn't seem ready to me - they should of waited until it was ready instead of sticking to some deadline imposed by marketing types.
The Rob Blog
Google Talk: robert.caldecott -
Alex Orovetskiy wrote:
MSDN...In short the design sucks. I prefered the one in Jan 2005
I simply hate MSDN Libray 2005! It's slow, I cannot find any interesting info, and the search filters don't work! When you select as languages C# and VB, the library offers results for JScript!!! Is this normal??? ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA] - eMule Server .NET
what's worst is that it is largely content-free. Look at the following code snippet:
// Gets or sets the size of the item, representing the width and height of a rectangle: public virtual System.Drawing.Size Size { get; set; }Now, every good developer would agree that both facts can be derived from the declaration as easy as from the comment, which makes the adduitional text useless. It's a content-free comment. Now look at this little gem[^]. What's the real contents? Gets or sets the size of the item. A Size, representing the width and height of a rectangle. covered in about over 200 words (counted by MS Office) That's of no use to me.
We say "get a life" to each other, disappointed or jokingly. What we forget, though, is that this is possibly the most destructive advice you can give to a geek.
boost your code || Fold With Us! || sighist -
what's worst is that it is largely content-free. Look at the following code snippet:
// Gets or sets the size of the item, representing the width and height of a rectangle: public virtual System.Drawing.Size Size { get; set; }Now, every good developer would agree that both facts can be derived from the declaration as easy as from the comment, which makes the adduitional text useless. It's a content-free comment. Now look at this little gem[^]. What's the real contents? Gets or sets the size of the item. A Size, representing the width and height of a rectangle. covered in about over 200 words (counted by MS Office) That's of no use to me.
We say "get a life" to each other, disappointed or jokingly. What we forget, though, is that this is possibly the most destructive advice you can give to a geek.
boost your code || Fold With Us! || sighistWell...of course you can get the meaning of the function and its parameters from it's declaration but it is always nice to have some extra explanation. -------------------------------- Human stupidity is infinite.
-
Alex Orovetskiy wrote:
MSDN...In short the design sucks. I prefered the one in Jan 2005
I simply hate MSDN Libray 2005! It's slow, I cannot find any interesting info, and the search filters don't work! When you select as languages C# and VB, the library offers results for JScript!!! Is this normal??? ___________________________________ Tozzi is right: Gaia is getting rid of us. My Blog [ITA] - eMule Server .NET
in the help window there is a cyan colored area at the top. in this area there is a "dropdown" titled "Language: Filter". Click that and choose which languages to filter on. Now this is just the examples to show in the help topic. Not what gets filtered in the search. The "Filtered by" combobox on the left pane does that.
-
Well...of course you can get the meaning of the function and its parameters from it's declaration but it is always nice to have some extra explanation. -------------------------------- Human stupidity is infinite.
My point is that there is absolutely no "extra explanation". There is not a single word that helps me use this property - how to initialize it for the derived classes (I was asking Help because I wondered why the form editor did initialize this for menu items), can it be left zero, in which unit it is, valid / invalid values etc. Drowning it in almost 200 words of boilerplate docs (though they are important) makes it worse: The doc is not only useless, but it also costs time to find out it's useless.
We say "get a life" to each other, disappointed or jokingly. What we forget, though, is that this is possibly the most destructive advice you can give to a geek.
boost your code || Fold With Us! || sighist
