Question

I am attempting to write a DLL using the C# .NET Framework 2.0. Everything compiles okay, but when I try to access the DLL from my application, it fails when attempting to get the procedure address. So, I oped the DLL in Dependency Walker, and all of my public functions are missing!

My DLL, so far, is fairly straightforward:

namespace MyDll_Namespace
{
    public class MyDllClass
    {
        public static int Func1( /* params */ ) { /* ... */ }

        public static int Func2( /* params */ ) { /* ... */ }

        public static int Func3( /* params */ ) { /* ... */ }

        public static int Func4( /* params */ ) { /* ... */ }
    }
}

There’s not much else, just a few constants and delegates defined inside the class, as well as outside the class in the namespace. Any thoughts or suggestions would be much appreciated. Thanks.

Answer 1

I decided to write my DLLs in C++. However, here is a bunch of useful information I found for using managed code from unmanaged code:

• Is it possible to use a DLL created using C# in an unmanaged VC++ application?
• How do I call C++/CLI (.NET) DLLs from standard, unmanaged non-.NET applications?
• Using managed code in an unmanaged application
• Using Managed Components from Unmanaged Code
• An Overview of Managed/Unmanaged Code Interoperability
• Unmanaged Exports
• Calling Managed .NET C# COM Objects from Unmanaged C++ Code
• All-In-One Code Framework
• CLR Hosting APIs
• How To: Migrate to /clr
• How to call a managed DLL from native Visual C++ code in Visual Studio.NET or in Visual Studio 2005