VC++ - VC#

[C G S Reddy]

Hi,

I have to develop an application which involves lot of GUI. I have the
sufficient skills in both VC++ 6.0 and VC#. I have developed applications
using VC++6.0 earlier. Is it worth to develop new applications in VC# through
which I can get advatages of garbage collection, managed code etc.,? or Shall
I continue to develop in VC++6.0.

Can somebody break this confusion?

By,
C G S Reddy.

[Rodrigo Corral [MVP]]

Why not use managed C++ and get the best of both worlds?
--
Un saludo
Rodrigo Corral González [MVP]

FAQ de microsoft.public.es.vc++
http://rcorral.mvps.org

[Peter van der Goes]

"C G S Reddy" <CG******@discussions.microsoft.com> wrote in message
news:CE**********************************@microsof t.com...

Hi,

I have to develop an application which involves lot of GUI. I have the
sufficient skills in both VC++ 6.0 and VC#. I have developed applications
using VC++6.0 earlier. Is it worth to develop new applications in VC#
through
which I can get advatages of garbage collection, managed code etc.,? or
Shall
I continue to develop in VC++6.0.

Can somebody break this confusion?

By,
C G S Reddy.

I agree with Rodrigo.
The choice between C++ and C# is primarily about platform dependence. C# is
a .NET language, pure and simple (yes, I know it's possible to write
unmanaged C# code...), while C++ allows you to choose between .NET, MFC, Win
API, etc. So, if your target is only .NET, consider C# for its new features
and ease of use. Otherwise, C++. What I can't figure out is why you haven't
moved to VS .NET 2003 and the new VC 7.1 compiler, which is more
standards-compliant than previous versions (and just better, IMHO).

--
Peter [MVP Visual Developer]
Jack of all trades, master of none.

[Ioannis Vranos]

Peter van der Goes wrote:

I agree with Rodrigo.
The choice between C++ and C# is primarily about platform dependence. C# is
a .NET language, pure and simple (yes, I know it's possible to write
unmanaged C# code...), while C++ allows you to choose between .NET, MFC, Win
API, etc. So, if your target is only .NET, consider C# for its new features
and ease of use. Otherwise, C++. What I can't figure out is why you haven't
moved to VS .NET 2003 and the new VC 7.1 compiler, which is more
standards-compliant than previous versions (and just better, IMHO).

C# has nothing more to offer than C++ in .NET. Especially after C++/CLI,
C# will provide less.
Another thing that I think will be funny in the WinFX era is C#/VB vs
XAML. Since XAML will exist, why would anyone learn VB or C#?
XAML will be a *compiled* .NET language in the style:
<Window>
<Button>
"OK"
</Button>
</Window>


--
Ioannis Vranos

[Rodrigo Corral [MVP]]

I completely agree!!!

--
Un saludo
Rodrigo Corral González [MVP]

FAQ de microsoft.public.es.vc++
http://rcorral.mvps.org

[Tim Robinson]

Ioannis Vranos wrote:
[...]

C# has nothing more to offer than C++ in .NET. Especially after C++/CLI,
C# will provide less.
I disagree. In my opinion as somebody who has been paid to write C++ for
many years, and C# for just over a year, C# has much better syntax for
expressing the sorts of constructs you use day-to-day. C++ is handy for
the more obscure stuff.
Another thing that I think will be funny in the WinFX era is C#/VB vs
XAML. Since XAML will exist, why would anyone learn VB or C#?

[...]

Because XAML is XML, and XML is not the perfect solution to every
problem that some seem to think it is.

--
Tim Robinson (MVP, Windows SDK)
http://mobius.sourceforge.net/

[Ioannis Vranos]

Tim Robinson wrote:

I disagree. In my opinion as somebody who has been paid to write C++ for
many years, and C# for just over a year, C# has much better syntax for
expressing the sorts of constructs you use day-to-day. C++ is handy for
the more obscure stuff.

Please provide an example. What better syntax C# provides in place of
ref class?
On the other hand it does not provide any syntax for compile-time
templates and lacks implicit deterministic destruction as two examples.


--
Ioannis Vranos

[Rodrigo Corral [MVP]]

Using C++, especially the new C++/CLI which is coming with VS2005, you have
the better of two worlds, managed and unmanaged, you can mix this two
worlds, and you have all the power of C++ and STL in your hands.

But I don't believe in religious fights about programming lenguages, even
less in the managed world. Use the lenguage you want, each lenguage have
advantages and drawbacks, but diferences between lenguages are few in .Net.

One thing is absolutly true, you can do things in VC++/CLI that are very
hard to do in other lenguages, but the opposite is not certain, without
considering asp.net.
--
Un saludo
Rodrigo Corral González [MVP]

FAQ de microsoft.public.es.vc++
http://rcorral.mvps.org

[Chris Stankevitz]

I would not recommend going with visual studio .net 2003 7.1 if your
application is large. My application has about 80 projects and takes much
longer to compile and much much longer to link than VC6. Apparently there's
a new version coming out which has more reasonable compile/link/IDE times.

Chris

"C G S Reddy" <CG******@discussions.microsoft.com> wrote in message
news:CE**********************************@microsof t.com...

Hi,

I have to develop an application which involves lot of GUI. I have the
sufficient skills in both VC++ 6.0 and VC#. I have developed applications
using VC++6.0 earlier. Is it worth to develop new applications in VC#
through
which I can get advatages of garbage collection, managed code etc.,? or
Shall
I continue to develop in VC++6.0.

Can somebody break this confusion?

By,
C G S Reddy.