dotnet newbie question -- visual c libraries

visual c libraries : dotnet newbie question

Jenny
7/13/2003 9:22:10 AM

I have been programming in C++/MFC/ATL for nearly 8 years now. I'm in the
process of learning .NET and am wondering if I should use VisualC++.Net or
C#. Are there any advantages/disadvantages going with one not the other OR
does it not really matter????

Thanks in Advance

Jenny.

Alvin Bruney
7/13/2003 10:48:22 AM

I think you should get away from the C++ personally, and get into C# full
fledged. The syntax is simpler for one, which leads to less programmatic
errors. It's less frustrating in a nutshell and there is tighter integration
with .NET since there is less unmanaged code to muck with in C# as opposed
to C++. On the other hand if you are into time critical systems etc, .NET
C++ is the way to go.

[quoted text, click to view]

geiger
7/13/2003 4:49:53 PM

hey
I don't think so - C# and C++ are very similar languages, but C# is
definitely more simply.
One of suppose dot net platform is "language is only syntax" ... unimportant
is if you write in C++ or C# because your managed code is compiled just
during starting your application.
C# is my choice ( VC++ .net 2002 don't have itegrated WindowsForms editor,
VC# 2002 of course have it )....
Sorry for my english - I'm elementary.

Przemek Mañkowski
Poland

[quoted text, click to view]

Manish Agarwal
7/13/2003 5:01:19 PM

Conceptwise both languages are totally different. Your question is something
like VC++ or Java

-------------------------
"Manish Agarwal"- <manishkrishan@hotmail.com>
http://personal.vsnl.com/mkag
If replying to the group, please do not mail me.

[quoted text, click to view]

Philip Braun
7/13/2003 7:23:38 PM

I am currently in that transition myself. Let me just note that .Net is not
a mature environment by any means yet. There are some things that have not
been included thus far. As an example, try to find any class in C# that can
open and use a serial port with, without using P/Invoke in the currently
available versions of .Net.

If you have any device interaction, sticking with C/C++ is a much better
bet. Although C# can do it, you will be calling C/C++ routines. If your
product is an office use only type program, then C# may be just for you. It
all depends on how much work you want to do. If your considering a re-write
in anycase to take advantage of the features that you now know about as
requested by your customer(s), then attempt to note which technology will be
around the longest and try to use that one. It looks like .Net is not a
flash in the pan and will cause another round of re-writes by the industry.

Phil

[quoted text, click to view]

Falcon Kirtarania
7/20/2003 6:06:26 PM

Just to step in here, would somebody mind telling me what the equivalent to
free(void *) or delete(void *) is in C#?

"Alvin Bruney" <vapordan_spam_me_not@hotmail_no_spamhotmail.com> wrote in
message news:e$N71YVSDHA.304@tk2msftngp13.phx.gbl...
[quoted text, click to view]

baba
7/25/2003 3:33:56 AM

Visual c++ 2003 now has windows form designer like all=20
other dotnet languages.
With visual c++, you are not tied to windows only unlike c#
My two cents<BG>
Baba
[quoted text, click to view]

Jan Roelof de Pijper
9/18/2003 2:19:20 PM

My two cents: At the moment, a commitment to C# seems to be a commitment to
the MS Windows platform. If you are or get proficient with C++, you leave
open your access to other platforms, such as Unix, Linux, Mac, whatever. At
the same time, you can still fully participate in .NET. So, opting for
VC++.NET may be the more difficult choice, but gives you maximum
flexibility.

Jan Roelof

[quoted text, click to view]

bob holder
11/5/2003 8:42:09 AM

[quoted text, click to view]

Well spoken Jon. The ability to program cross platform with C/C++ on unix,
linux, windows, embedded, etc opens all doors. Sticking with C# is much too
restrictive these days.
bob

Google_Post NO[at]SPAM slink-software.com
11/6/2003 8:06:58 AM

[quoted text, click to view]

Other questions for dotnet:

1) Which Windows platform does it support without the user downloading a
the dotnet framework? Win9x? WinNT?, Win2k, or is it XP only?

What's the smallest user OS requirements (without patch) for me to deploy a
dotnet app?

2) When I tried to instead some sample app a while back, it requires me to
download about few differents frameworks, patches to OS, etc before I can even
run the application. Is that still the case if I want to run any dotnet
application?

If so, the framework is as bad if not worst that Java.

--
SLink generates hyperlinks for all functions, macros, variables from
thousands of src file. Browse hyperlinked source code for .NET CLI,
Mozilla, Apache, NetBSD, Ethereal, Chorus OS, TCL, Python, PHP at

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about visual c libraries

home · blog · groups

Questions? Comments? Contact the dn