Click here to Skip to main content
13,627,791 members
Click here to Skip to main content
Add your own
alternative version

Stats

334.1K views
3.7K downloads
91 bookmarked
Posted 9 Nov 2006
Licenced CPOL

How to Automate Exporting .NET Function to Unmanaged Programs

, 21 Nov 2006
Rate this:
Please Sign up or sign in to vote.
Post-build tool which can automate exporting .NET function to unmanaged programs

Introduction

Exporting functions to unmanaged programs - why not? I don't want to change *.il files by hand. I need to automate this. So here we go...

Background

A few days ago, I was writing a program (Terminal Services addin). The first problem was that I couldn't write this in C# ... Ok. I started writing it in C++/CLI. But there was another problem - mstsc.exe doesn't like to load such a library. Ok. No problem. I started another project (in C++/CLI - the first I change to pure C++) which exports one function. The first library loaded the second one and everything worked. But for dependencies, I needed easy deployment without installing VC80 runtimes... So I tried to find a way to export the function from C#. And I found it. While I was working with a project, I compiled it often and changing *.il files by hand was really annoying. That's why I made this tool. (Anyway later I found that the first library can be written in C# but it is a topic for another article - "How to write Terminal Services addin in pure C#" .)

Using the Code

Well the code is just the code ... it's a home-grown parser with some other functionality... So I'll rather write how to use it (and sometimes how it works).

Beginning

What you need to use it:

  • Framework 2.0 SDK
  • Visual Studio 2005 (optional)

First you should download the code (there are two projects ExportDll.exe and ExportDllAttribute.dll) and build it.

Then you should know how to use it... After creating the library project in C# or VB.NET, you need to add dependency to ExportDllAttribute. "Oh no, not another dependency" - you'll say. Easy ... just wait ... This library contains an attribute which tells ExportDll.exe that some function needs to be exported.

How It Works

As I said, ExportDll.exe needs to know which functions need to be exported. So you'll write something like this:

public class SomeClassName
{
    //second parameter of attribute is calling convention,
    //default is StdCall but u can use others fx.:
    [ExportDllAttribute.ExportDll("ExportNameOfFunction",
    System.Runtime.InteropServices.CallingConvention.Cdecl)]
    public static void SomeFunctionName()
    {
        System.Console.WriteLine("I really do nothing");
    }
}

After compiling, you need to use ExportDll tool to export this:

ExportDll.exe full_path_to_yours_dll\yoursdll.dll [/Release|/Debug]

Note: /Release flag is default. What exactly does ExportDll do:

  • Reads DLL as assembly and makes a dictionary of exported function
  • Decompiles DLL
  • Searches and replaces some stuff in IL code (If you want to know what, read the article that I mentioned in the "Background" section.)
  • Deletes ExportDllAttribute dependency

    .assembly extern ExportDllAttribute
    {
      .ver x:x:x:x
    }

    and

    .custom instance void
        [ExportDllAttribute]ExportDllAttribute.ExportDllAttribute ...
  • Compiles modified IL code again

Post-building in Visual Studio 2005

How? It's easy... Just add in Project property named "Post-build event command".

"path_to_tools\ExportDll.exe" "$(TargetPath)" /$(ConfigurationName)

OMG! It's Not Working

Hmm... Yes, forgot to mention about ExportDll.exe.cofig ...

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <configSections>
        <sectionGroup name="applicationSettings" 

        type="System.Configuration.ApplicationSettingsGroup, 
        System, Version=2.0.0.0, Culture=neutral, 
        PublicKeyToken=b77a5c561934e089" >
            <section name="ExportDll.Properties.Settings"

        type="System.Configuration.ClientSettingsSection,
        System, Version=2.0.0.0, Culture=neutral,
        PublicKeyToken=b77a5c561934e089" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <applicationSettings>
        <ExportDll.Properties.Settings>
            <setting name="ildasmpath" serializeAs="String">
                <value>C:\Program Files\
                Microsoft Visual Studio 8\SDK\v2.0\Bin\ildasm.exe</value>
            </setting>
            <setting name="ilasmpath" serializeAs="String">
                <value>C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ilasm.exe
                </value>
            </setting>
        </ExportDll.Properties.Settings>
    </applicationSettings>
</configuration>

You need to configure path to ilasm and ildasm.

Updates

New version

  • now accept MarshalAsAtrribute
  • new commands in command line support: first had to be TargetPath then you can add:
    /release or /debug - /release id default
    /AnyCPU or /x64 - /AnyCPU is default its for 32/64 bit (for itanium add /PE64 /ITANIUM)
    ... any valid command for ildasm.exe
  • support fo x64
    "path_to_tools\ExportDll.exe" "$(TargetPath)" /$(ConfigurationName) /$(PlatformName)
    if PlatformName == "AnyCPU" then compiles for 32 bit
    if PlatformName == "x64" then compiles for 64 bit
  • now its compiled for runtime 4.0(ExportDll.exe) and 2.0 (ExportDllAttribut.dll) so it should be working for frameworks 2.0 - 4.0
  • it can compile for 2.0 or 4.0 runtime (runtime its not framework - frm 3.0 and 3.5 are using 2.0 runtime)
    it can be change by changing ilasmpath setting so:
    2.0 => C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\ilasm.exe
    4.0 => C:\Windows\Microsoft.NET\Framework\v4.0.30319\ilasm.exe

References

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Share

About the Author

Selvin
Systems / Hardware Administrator
Poland Poland
No Biography provided

You may also be interested in...

Comments and Discussions

 
QuestionEvents Pin
fayring6-Jun-09 22:37
memberfayring6-Jun-09 22:37 
GeneralExporting Errors in VB.NET, prolly my stupidity... Pin
Juvenal1-Apr-09 15:58
memberJuvenal1-Apr-09 15:58 
GeneralUnable to load one or more of the requested types Pin
normanr25-Jan-09 4:55
membernormanr25-Jan-09 4:55 
GeneralRe: Unable to load one or more of the requested types Pin
normanr25-Jan-09 5:21
membernormanr25-Jan-09 5:21 
QuestionExporting problem using the "DLLExport"-Function Pin
saplpete1-Dec-08 10:15
membersaplpete1-Dec-08 10:15 
AnswerRe: Exporting problem using the "DLLExport"-Function Pin
Selvin3-Dec-08 5:45
memberSelvin3-Dec-08 5:45 
GeneralRe: Exporting problem using the "DLLExport"-Function Pin
saplpete7-Dec-08 0:24
membersaplpete7-Dec-08 0:24 
GeneralRe: Exporting problem using the "DLLExport"-Function Pin
saplpete10-Dec-08 7:54
membersaplpete10-Dec-08 7:54 
The problems don't want to disappear! I changed my code like this:

using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Runtime.InteropServices;

namespace ZufallArray
{
    public class ZufallArray
    {
        [ExportDllAttribute.ExportDll("ZArray",
        System.Runtime.InteropServices.CallingConvention.Cdecl)]

        //Applied to a return value.
        [return:MarshalAs(UnmanagedType.LPArray, SizeParamIndex=1)]
        public static int[] ZArray(int beginn, int ende, int anzahl)
        {
            int[] ZZahl = new int[anzahl]; 
            Random randObj = new Random();
            for (int j = 0; j < anzahl; j++)
            {
                ZZahl[j]= randObj.Next(beginn, ende);
            }
            return ZZahl;
        }
    }
}


When I start the "ExportDll.exe" on commandline I get the following error:

"Nicht verifizierbarer Code hat die Richtlinienüberprüfung nicht bestanden. (Ausnahme von HRESULT: 0x80131402)"

Dependency Walker don't show any exported function!

P.S.: As nobody can help me I am forced to abandon.

Peter
GeneralRe: Exporting problem using the "DLLExport"-Function Pin
Selvin10-Dec-08 11:24
memberSelvin10-Dec-08 11:24 
GeneralRe: Exporting problem using the "DLLExport"-Function Pin
saplpete11-Dec-08 10:17
membersaplpete11-Dec-08 10:17 
GeneralRe: Exporting problem using the "DLLExport"-Function Pin
Selvin11-Dec-08 12:14
memberSelvin11-Dec-08 12:14 
GeneralRe: Exporting problem using the "DLLExport"-Function Pin
saplpete12-Dec-08 10:59
membersaplpete12-Dec-08 10:59 
QuestionRe: Exporting problem using the "DLLExport"-Function Pin
Filip Vande Weghe15-Jul-09 1:22
memberFilip Vande Weghe15-Jul-09 1:22 
AnswerRe: Exporting problem using the "DLLExport"-Function Pin
Filip Vande Weghe16-Jul-09 4:57
memberFilip Vande Weghe16-Jul-09 4:57 
QuestionRe: Exporting problem using the "DLLExport"-Function Pin
mla1547-Feb-13 10:02
membermla1547-Feb-13 10:02 
AnswerRe: Exporting problem using the "DLLExport"-Function Pin
mla1548-Feb-13 5:43
membermla1548-Feb-13 5:43 
Questionmissing dependencies Pin
Magick9323-Sep-08 9:39
memberMagick9323-Sep-08 9:39 
AnswerRe: missing dependencies Pin
Selvin24-Sep-08 0:23
memberSelvin24-Sep-08 0:23 
Questionhow can I build it in vc6++? Pin
K.O.17-Aug-08 5:25
memberK.O.17-Aug-08 5:25 
GeneralExport VB dll in Visual Studio 2008 Pin
paolopagano30-Jul-08 0:19
memberpaolopagano30-Jul-08 0:19 
GeneralRe: Export VB dll in Visual Studio 2008 Pin
plsmith51214-Jan-09 4:16
memberplsmith51214-Jan-09 4:16 
GeneralExport DLL in Visual Studio 2008 Pin
paolopagano29-Jul-08 23:43
memberpaolopagano29-Jul-08 23:43 
Questioncan works in 64 bits Pin
manuel.alvarez3-Jun-08 1:06
membermanuel.alvarez3-Jun-08 1:06 
AnswerRe: can works in 64 bits Pin
Selvin3-Jun-08 2:10
memberSelvin3-Jun-08 2:10 
GeneralRe: can works in 64 bits Pin
Selvin12-Jun-08 20:48
memberSelvin12-Jun-08 20:48 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.

Permalink | Advertise | Privacy | Cookies | Terms of Use | Mobile
Web03 | 2.8.180712.1 | Last Updated 22 Nov 2006
Article Copyright 2006 by Selvin
Everything else Copyright © CodeProject, 1999-2018
Layout: fixed | fluid