Hi quortex!
> I have created a very small test wrapper class in Managed C++ which
> wraps up some very simple native code. I am using C# 2 + Visual Studio
> 2005 Beta 2.
What project-type have you created?
For a C++/CLI assembly project you should take a "C++|CLR|Class Library"
project (File|New|Project...)
In the project properties under the "general" entry the should be the
following:
- Configuration Typ: Dynamic Library (DLL)
- Common language runtime support: Common Language Runtime Support (/clr)
And in the "Linker|General" there should be the pathe/filename of the
generated DLL.

Signature
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
quortex - 20 Sep 2005 10:16 GMT
Hi,
Thanks for the reply. I just checked my project just incase but as I
thought yes I have a managed c++ project. It has /clr switch and is set
to be a DLL with linker output of $(OutDir)\$(ProjectName).dll.
It is outputting the .manifest file so I guess that's another sign it's
setup correctly. Perhaps I have missed something with the internal
structure of my library it just contains two classes and their
corresponding header files. Everything is very simple very clean with
no warnings or errors.
This is really holding me up and driving me mad to be honest. Any
ideas?
Kind Regards,
Mark
Jochen Kalmbach [MVP] - 20 Sep 2005 10:33 GMT
Hi quortex!
> it just contains two classes and their
> corresponding header files. Everything is very simple very clean with
> no warnings or errors.
What classes? Managed or Unmanaged?
You need to have at least a managed class!
Can you post a small code-snipped?

Signature
Greetings
Jochen
My blog about Win32 and .NET
http://blog.kalmbachnet.de/
quortex - 20 Sep 2005 10:37 GMT
Jochen,
DOH!
My apologies I can't believe it the dll was being outputted but it was
being outputted to a debug folder of the solution root rather than the
project root.
I did a search for the dll and found it :( Tragic tragic it was working
all along.
Thanks for your help.
Mark