Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Languages / Managed C++ / October 2007

Tip: Looking for answers? Try searching our database.

Expiry date for microsoft support on vc++?

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Rajeshaz09 - 26 Oct 2007 04:32 GMT
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 - 26 Oct 2007 09:47 GMT
> 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.

Signature

David Wilkinson
Visual C++ MVP

David Lowndes - 26 Oct 2007 11:15 GMT
>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] - 26 Oct 2007 18:37 GMT
> >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]
>
> Dave

In that case they're simply going to tell you to use VC++ 8.0 or 9.0.
David Lowndes - 26 Oct 2007 20:50 GMT
>> >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.

Exactly :)
Rajeshaz09 - 27 Oct 2007 06:14 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?

> >> >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 ...

Rate this thread:







Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.