Member Avatar for DotNetUser

I'm new to Visual Studio .NET. I thought C#.NET replaces VC++ 6.0 until I saw that C++.NET was still around. So, what's the difference between the two? I want to create a GUI that uses some C++ header/source files and a C++ socket library. Which would I use? I have VB 6.0 experience but very minimal VC++ 6.0 experience. Thanks.

  • 4 Contributors
  • 5 Replies
  • 253 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by darklordsatan

Dani AI

Generated

Short answer for : C++.NET (the Visual C++ language extensions usually called C++/CLI) is a version of C++ that can compile both native and managed code in the same assembly, so it is the natural bridge for reusing VC++ headers and existing C++ libraries with minimal changes. C# is a pure managed .NET language and is the more productive choice for building Windows Forms or WPF UIs and general application logic. (learn.microsoft.com)

Integration options and tradeoffs (ties back to comments from and ):

  • If the socket library exposes C-style exported functions, call it directly from managed code with P/Invoke (simple but only convenient for C APIs). (learn.microsoft.com)
  • If the library is C++ with classes, the usual approach is a thin C++/CLI “wrapper” assembly: include the native headers and link the native libs in a C++/CLI project, then expose small managed ref classes that the UI can consume. This avoids massive rewrites and keeps interop code in one place. (learn.microsoft.com)

Practical workflow and cautions (compact, applicable years later):

  1. Create the UI in C# (WinForms or WPF) to get the designer/tooling benefits.
  2. Create a Visual C++ Class Library compiled with C++/CLI (/clr or /clr:netcore as appropriate), include the existing headers, link the native socket library, and implement managed wrapper types that forward to native code.
  3. Reference the C++/CLI DLL from the C# project and call the managed wrappers.
    Watch for platform and runtime issues: build configurations (x86 vs x64) must match, CRT/runtime dependencies and calling conventions must be correct, and native resource lifetime should be exposed via IDisposable on wrappers. For porting and mixed-mode rules see Microsoft guidance. (learn.microsoft.com)

Summary recommendation: for a GUI that must reuse existing VC++ headers and a native socket library, prefer a C# UI plus a small C++/CLI wrapper. If cross-platform deployment is required or C++/CLI cannot be used, provide a stable C-style DLL or COM surface and use P/Invoke or COM interop instead. Note that C++/CLI support and mixed-mode assemblies are effectively Windows-focused in modern .NET tooling—plan accordingly. (learn.microsoft.com)

Recommended Answers

All 5 Replies

Member Avatar for DotNetUser

Do you know which (C#.NET or C++.NET) would be able to integrate C++ 6.0 header/source files without any changes?

Member Avatar for Dave Sinkula

No, I don't.

Member Avatar for shre86

c++.net should be able to use all the headers of vc++..

Member Avatar for darklordsatan

C++ is a programming language
C# is another programming language

Thus, C++ .Net is the replacement for VC++ 6.0
C# .NET is just a new platform, so It has nothing to do with VC++ 6.0

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.