Will Visual C++ be replaced by C# Completely?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am new in Visual C++ and I heard that Visual C++ will be replaced by c#.
Is that real? Microsoft will no longer support Visual C++?
 
hi,

no way, c/c++ and c# covers two differents sectors and will coexist without
any problem. as far as the current computing structure exist C/C++ will be
around :)


cheers,
 
Not in the foreseeable future, Microsoft has lots of C++ code (Windows,
Office) that will need to be supported, and beyond that Windows drivers
require C/C++.

--
Best regards,

Carlos J. Quintero

MZ-Tools: Productivity add-ins for Visual Studio .NET, VB6, VB5 and VBA
You can code, design and document much faster.
Free resources for add-in developers:
http://www.mztools.com
 
paul388 said:
I am new in Visual C++ and I heard that Visual C++ will be replaced by c#.
Is that real? Microsoft will no longer support Visual C++?
Click to expand...

Whoever told you that is apparently not aware the C# is a .NET - only
language vs. C/C++ which are capable of producing applications which are
independent of any runtime support. Another factor mitigating against any
such replacement is the existence of millions of lines of C/C++ code in
thousands of applications that it makes no sense to convert/rewrite from an
economic standpoint.
If you are referring to within .NET only, the signs in VS 2005 also refute
what you heard. Microsoft has invested heavily in enhancements to managed
C++ (C++ CLI) in the new version to be released in early November.
 
Perhaps whoever told you had the right idea, but the wrong language. VB will
no longer be supported (at least that is the story right now).

This may be a bit of an aside, and is meant as information, not as a
soapbox.

Many of the same arguments made by Pete (below) also apply to VB. There are
also millions of lines of VB code that will suddenly become obsolete, without
any migration pattern (VB.NET does not offer an upgrade to previous VB
products).

There is a strong push by the VB community to have Microsoft develop a .NET
version of "classic" VB (you may hear of VB.COM, which is one possible name
for this version).

A virtual petition is available at http://classicvb.org/petition/ which
explains more.
Whoever told you that is apparently not aware the C# is a .NET - only
language vs. C/C++ which are capable of producing applications which are
independent of any runtime support. Another factor mitigating against any
such replacement is the existence of millions of lines of C/C++ code in
thousands of applications that it makes no sense to convert/rewrite from an
economic standpoint.
Click to expand...
Peter [MVP Visual Developer]
Jack of all trades, master of none.
Click to expand...
 
pagates said:
Perhaps whoever told you had the right idea, but the wrong language. VB
will
no longer be supported (at least that is the story right now).
Click to expand...
Do you have some links to support the supposition that VB will no longer be
supported? I'm not trying to be argumentative, I just haven't heard that as
yet. Thanks.
 
Sure.

According to Microsoft, mainstream support ended March 31, 2005. Extended
support ends March 31, 2008:

http://support.microsoft.com/default.aspx/gp/lifeprodv

Also, the FAQ section of the "Classic VB" site (the site that has the
petition) also has some information spelled out more elegantly than I could
attempt:

http://classicvb.org/petition/faq.asp

Keep in mind that one of the biggest problems isn't just that VB the
language isn't going to be supported, but that the applications and customer
data created by these applications will not be supported.
 
pagates said:
Sure.

According to Microsoft, mainstream support ended March 31, 2005. Extended
support ends March 31, 2008:
Click to expand...
Ah yes, VB !.NET ;) (VB6)
I also was confused by your original statement.
I still class VB .NET as VB (Just not unmanaged/classic/6,5,4)

JB
 
Thanks for all your answers, Currently I am using VC++ 6 for my project, but
I heard that Visual Studio 6 is the last version to support VC++, the next
version up is Visual Studio .net and there is no VC++ component in it.

I just wonder should I need to invest my time to learn a new language C#
again. Is there any migration tool for vc++ to c# to make life easier?
 
paul388 said:
Thanks for all your answers, Currently I am using VC++ 6 for my project, but
I heard that Visual Studio 6 is the last version to support VC++, the next
version up is Visual Studio .net and there is no VC++ component in it.

I just wonder should I need to invest my time to learn a new language C#
again. Is there any migration tool for vc++ to c# to make life easier?
Click to expand...
VC++ is still supported (VS 2003), not quite sure about VS 2005 but I
presume as others have said that it would be.
There are a couple of options for VC++ in the VS 2003 environment.
ATL, MFC, .NET, etc..
JB
 
pagates said:
Sure.

According to Microsoft, mainstream support ended March 31, 2005. Extended
support ends March 31, 2008:

http://support.microsoft.com/default.aspx/gp/lifeprodv

Also, the FAQ section of the "Classic VB" site (the site that has the
petition) also has some information spelled out more elegantly than I
could
attempt:

http://classicvb.org/petition/faq.asp

Keep in mind that one of the biggest problems isn't just that VB the
language isn't going to be supported, but that the applications and
customer
data created by these applications will not be supported.
Click to expand...
Ah! I see now. You were referring to "classic" VB, not VB.NET.
Thanks.
 
paul388 said:
Thanks for all your answers, Currently I am using VC++ 6 for my project,
but
I heard that Visual Studio 6 is the last version to support VC++, the next
version up is Visual Studio .net and there is no VC++ component in it.

I just wonder should I need to invest my time to learn a new language C#
again. Is there any migration tool for vc++ to c# to make life easier?
Click to expand...
Not sure where you heard that, but I can assure you that VC++ (referring to
the C++ language) is fully supported in Visual Studio 2003 and 2005. AAMOF,
Microsoft has invested heavily in improvements to the C++ compiler, in terms
of standards compliance (2003), improved code security (2005) and managed
code (now CLI for VS 2005) features.
Nothing wrong with learning C# as well, but I don't believe C++ is going
away anytime soon.
 
Back
Top