How to convert a VC# .NET project into a VC++ .NET project

[Kueishiong Tu]

I have a VC# .NET project which is imported from an OCX control using AxImp.
I would like to convert it into a VC++ .NET project. Is there any way to do
it and how to do it?

 

[David Anton]

We produce Instant C++ C# Edition. You can download the demo at:
http://www.tangiblesoftwaresolutions.com/Demo.htm
--
http://www.tangiblesoftwaresolutions.com
C++ to C#
C++ to VB
C++ to Java
C++ to C++/CLI
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: convert VB or C# to C++/CLI

 

[Kueishiong Tu]

Dear David:

Do you have "Instant C++: convert VB or C# to C++/CLI"
product that works in the .NET Framework 1.1 platform?

 

[David Anton]

No. There was so little demand for conversion to Managed C++, that we
limited Instant C++ to conversion to C++/CLI, which of course requires .NET
Framework version 2 or higher.
--
http://www.tangiblesoftwaresolutions.com
C++ to C#
C++ to VB
C++ to Java
C++ to C++/CLI
Instant C#: VB to C# converter
Instant VB: C# to VB converter
Instant C++: convert VB or C# to C++/CLI

 

[Ben Voigt [C++ MVP]]

Dear David:

Do you have "Instant C++: convert VB or C# to C++/CLI"
product that works in the .NET Framework 1.1 platform?

The C++ compiler targetting .NET Framework 1.x was badly broken, considered
unfixable by Microsoft. Fixing the problems required not only a new
compiler but also sweeping changes to the runtime. These changes are
included in .NET 2.0. In fact, all the "workarounds" for the Managed
Extensions for C++ require using .NET 2 or later.

p/invoke and COM are the only reliable methods of interop in .NET 1.x

The upgrade from .NET 1.x to .NET 2.0 isn't optional like upgrading Office,
it's more like upgrading Internet Explorer where there are critical security
improvements and bug fixes included in the new version.