Expiry date for microsoft support on vc++?

[=?Utf-8?B?UmFqZXNoYXowOQ==?=]

I heared that microsoft give technical support to vb upto this year end. Can
any one microsoft stops techinical support for vc++(6.0)? was microsoft
announced any official date?

[David Wilkinson]

Rajeshaz09 wrote:

I heared that microsoft give technical support to vb upto this year end. Can
any one microsoft stops techinical support for vc++(6.0)? was microsoft
announced any official date?

Rajehaz:

Technical support for VC6 ended long ago. But you really do not need it.
These newsgroups, CodeProject, Google, etc have everything you need.

--
David Wilkinson
Visual C++ MVP

[David Lowndes]

>Technical support for VC6 ended long ago. But you really do not need it.

>These newsgroups, CodeProject, Google, etc have everything you need.

Except for the official support you may have been able to get from MS
should you encounter an issue that would require them to create a
hotfix - possibly a highly unlikely situation!

Dave

[Ben Voigt [C++ MVP]]

"David Lowndes" <Da****@example.invalidwrote in message
news:3c********************************@4ax.com...

Technical support for VC6 ended long ago. But you really do not need it.
These newsgroups, CodeProject, Google, etc have everything you need.

Except for the official support you may have been able to get from MS
should you encounter an issue that would require them to create a
hotfix - possibly a highly unlikely situation!

Dave

In that case they're simply going to tell you to use VC++ 8.0 or 9.0.

[David Lowndes]

>Technical support for VC6 ended long ago. But you really do not need it.

>>>These newsgroups, CodeProject, Google, etc have everything you need.

Except for the official support you may have been able to get from MS
should you encounter an issue that would require them to create a
hotfix - possibly a highly unlikely situation!

In that case they're simply going to tell you to use VC++ 8.0 or 9.0.

Exactly :)

[=?Utf-8?B?UmFqZXNoYXowOQ==?=]

http://weblogs.asp.net/jackieg/archi...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?
"David Lowndes" wrote:

Technical support for VC6 ended long ago. But you really do not need it.
These newsgroups, CodeProject, Google, etc have everything you need.

Except for the official support you may have been able to get from MS
should you encounter an issue that would require them to create a
hotfix - possibly a highly unlikely situation!

In that case they're simply going to tell you to use VC++ 8.0 or 9.0.

Exactly :)

[Frank Hickman]

"Rajeshaz09" <Ra********@discussions.microsoft.comwrote in message
news:68**********************************@microsof t.com...

>
http://weblogs.asp.net/jackieg/archi...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?
"David Lowndes" wrote:

>Technical support for VC6 ended long ago. But you really do not need
it.
These newsgroups, CodeProject, Google, etc have everything you need.

Except for the official support you may have been able to get from MS
should you encounter an issue that would require them to create a
hotfix - possibly a highly unlikely situation!

In that case they're simply going to tell you to use VC++ 8.0 or 9.0.

Exactly :)

As David said before, direct support from Microsoft for VC6 has already
ended.

--
============
Frank Hickman
NobleSoft, Inc.
============
Replace the _nosp@m_ with @ to reply.

[David Wilkinson]

Rajeshaz09 wrote:

http://weblogs.asp.net/jackieg/archi...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.

--
David Wilkinson
Visual C++ MVP

[David Wilkinson]

David Wilkinson wrote:

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

And I forgot a biggie:

6. Safer computing (buffer overrun resistance).

I'm sure there are more ...

--
David Wilkinson
Visual C++ MVP

[=?Utf-8?B?UmFqZXNoYXowOQ==?=]

Thank you all :)
"David Wilkinson" wrote:

David Wilkinson wrote:

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

And I forgot a biggie:

6. Safer computing (buffer overrun resistance).

I'm sure there are more ...

--
David Wilkinson
Visual C++ MVP