Re: Channel 9 video: Visual C++ 10 is the new 6
I wish they would add StartsWith() and EndsWith() to CString. I'd do it
myself, but unfortunately CString (the new one we love) is not easy to
extend these days.
Overall I find CString and .NET::String pretty on par (only that difference
between using == and .Equals() always confuses me still).
Tom
"Ajay Kalra" <ajaykalra@yahoo.com> wrote in message
news:f1be5af8-f50f-4265-94df-9ed29eae5f0e@3g2000yqs.googlegroups.com...
On Nov 19, 3:26 pm, "David Ching" <d...@remove-this.dcsoft.com> wrote:
"Ajay Kalra" <ajayka...@yahoo.com> wrote in message
news:087bb955-7ce8-48c6-b92b-4754e268817e@g38g2000yqn.googlegroups.com...
The big advantage of using a newer version of Visual Studio than VC6 is
that the C++ compiler is much newer and much more compliant with the
ISO C++ language. That means that any third-party library code that you
may want to use in your projects is much more likely to compile.
I think that alone will justify the upgrade for most. I personally
dont think MFC enhancements have amounted to much after VC6.
I can't live without CStringA/W anymore. I got tired of manually creating
a
manifest just to use Common Controls 6. I don't have to delete the .ncb
file nearly as much as with VC6. I like my XML color coded. When I edit
Javascript, I like that color coded also. I like the Server Explorer to
manage my databases (was that in VC6?). The missing Find/Replace in Entire
solution is irksome. Visual Assist X integrates much better than in VS6. I
got used to the Consolas font. I got used to editing true color icons (and
Icon Workshop Lite only works with VS2008).
I never realized that I take all this and more for granted when I
moved to C#/.Net.
--
Ajay