>> >Technical support for VC6 ended long ago. But you really do not need it.
>>>These newsgroups, CodeProject, Google, etc have everything you need.
[quoted text clipped - 4 lines]
>
>In that case they're simply going to tell you to use VC++ 8.0 or 9.0.
http://weblogs.asp.net/jackieg/archive/2005/03/06/386065.aspx
see above link. In that they mentioned vb suppport end date.
My client have lot of applications (VC++). We need to tell him reasons for
migrating to VC++.net. Can any one know when microsoft ends support to vc++
6.0?
> >> >Technical support for VC6 ended long ago. But you really do not need it.
> >>>These newsgroups, CodeProject, Google, etc have everything you need.
[quoted text clipped - 6 lines]
>
> Exactly :)
Frank Hickman - 27 Oct 2007 06:59 GMT
> http://weblogs.asp.net/jackieg/archive/2005/03/06/386065.aspx
> see above link. In that they mentioned vb suppport end date.
[quoted text clipped - 15 lines]
>>
>> Exactly :)
As David said before, direct support from Microsoft for VC6 has already
ended.

Signature
============
Frank Hickman
NobleSoft, Inc.
============
Replace the _nosp@m_ with @ to reply.
David Wilkinson - 27 Oct 2007 10:27 GMT
> http://weblogs.asp.net/jackieg/archive/2005/03/06/386065.aspx
> see above link. In that they mentioned vb suppport end date.
>
> My client have lot of applications (VC++). We need to tell him reasons for
> migrating to VC++.net. Can any one know when microsoft ends support to vc++
> 6.0?
Rajesh:
I told you before: Microsoft support for VC6 is long ended.
What do you mean by "migrating to .NET"?
If you mean converting the applications (presumably currently MFC?) to
managed .NET applications, this would very likely be a big mistake.
If you mean just updating the code to a later version of the compiler,
note that only VS2002 and VS2003 had the confusing .NET name attached.
Visual Studio 2005 and 2008 do suffer from this "feature".
Reasons to update to a later version for native code:
1. Much better C++ conformance in the compiler
2. Better debugging experience
3. Can use latest versions of the Platform SDK
4. Some improvements in MFC (especially in VS2008 and beyond)
5. Better Unicode support
Compared to these, IMHO, official Microsoft support is a very minor issue.
If your client is still using VC6, it would make sense now to wait for
VS2008.

Signature
David Wilkinson
Visual C++ MVP
David Wilkinson - 27 Oct 2007 10:36 GMT
> Reasons to update to a later version for native code:
>
[quoted text clipped - 3 lines]
> 4. Some improvements in MFC (especially in VS2008 and beyond)
> 5. Better Unicode support
And I forgot a biggie:
6. Safer computing (buffer overrun resistance).
I'm sure there are more ...

Signature
David Wilkinson
Visual C++ MVP
Rajeshaz09 - 29 Oct 2007 02:43 GMT
Thank you all :)
> > Reasons to update to a later version for native code:
> >
[quoted text clipped - 9 lines]
>
> I'm sure there are more ...