.cpp and .cs in the same assembly

[Ken Durden]

Are there any plans in a future release of .NET to allow Managed C++
to co-exist in the same assembly with C# code?

The reason I ask is that I keep running into the problem where
conceptually speaking classes I make belong in a single DLL /
Assembly; due to the nature of their implementation, however, it is
frequently better to use either C# or MC++. In particular, I prefer to
use MC++ where its easier to interact with unmanaged C++. So, some DLL
which would be called Framework ends up being Framework_CS and
Framework_CPP, but that only works for simple cases, alot of times
Framework_CPP has dependencies on Framework_CS and vice versa; this
necessitates creating a bunch more DLLs than I had originally wanted
to only due to the language division.

Thanks,
-ken

[Nicholas Paldino [.NET/C# MVP]]

Ken,

C++ and C# code do not exist in assemblies. IL exists in assemblies.
Currently, only one programming language is allowed in any project type. By
default, projects in VS.NET compile into assemblies. However, you can
manually compile files to modules, and assemblies can have multiple modules.
This is currently the only way you can use different languages which compile
into the same assembly.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard.caspershouse.com
"Ken Durden" <cr*************@hotmail.com> wrote in message
news:18**************************@posting.google.c om...

Are there any plans in a future release of .NET to allow Managed C++
to co-exist in the same assembly with C# code?

The reason I ask is that I keep running into the problem where
conceptually speaking classes I make belong in a single DLL /
Assembly; due to the nature of their implementation, however, it is
frequently better to use either C# or MC++. In particular, I prefer to
use MC++ where its easier to interact with unmanaged C++. So, some DLL
which would be called Framework ends up being Framework_CS and
Framework_CPP, but that only works for simple cases, alot of times
Framework_CPP has dependencies on Framework_CS and vice versa; this
necessitates creating a bunch more DLLs than I had originally wanted
to only due to the language division.

Thanks,
-ken

[Frank Oquendo]

Nicholas Paldino [.NET/C# MVP] wrote:

However, you can manually compile files to modules, and
assemblies can have multiple modules. This is currently the only way
you can use different languages which compile into the same assembly.

Where can I find more info on this process?

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)