5,666,132 members and growing! (18,058 online)
Email Password   helpLost your password?
Platforms, Frameworks & Libraries » .NET Framework » General     Intermediate License: The Code Project Open License (CPOL)

How to Automate Exporting .NET Function to Unmanaged Programs

By Selvin

Post-build tool which can automate exporting .NET function to unmanaged programs
C#, VB, Windows, .NET, Visual Studio, Dev

Posted: 9 Nov 2006
Updated: 21 Nov 2006
Views: 27,621
Bookmarked: 33 times
Announcements
Loading...



Search    
Advanced Search
Sitemap
15 votes for this Article.
Popularity: 4.36 Rating: 3.71 out of 5
2 votes, 13.3%
1
2 votes, 13.3%
2
0 votes, 0.0%
3
1 vote, 6.7%
4
10 votes, 66.7%
5

Introduction

Exporting functions to unmanaged programs - why not?
But 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.

References

License

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

About the Author

Selvin



Occupation: Systems / Hardware Administrator
Location: Poland Poland

Other popular .NET Framework articles:

Article Top
Sign Up to vote for this article
You must Sign In to use this message board.
FAQ FAQ Noise ToleranceSearch Search Messages 
 Layout  Per page   
 Msgs 1 to 25 of 35 (Total in Forum: 35) (Refresh)FirstPrevNext
Questionmissing dependenciesmemberMagick9310:39 23 Sep '08  
AnswerRe: missing dependenciesmemberSelvin1:23 24 Sep '08  
Generalhow can I build it in vc6++?memberK.O.6:25 17 Aug '08  
GeneralExport VB dll in Visual Studio 2008memberpaolopagano1:19 30 Jul '08  
GeneralExport DLL in Visual Studio 2008memberpaolopagano0:43 30 Jul '08  
Generalcan works in 64 bitsmembermanuel.alvarez2:06 3 Jun '08  
GeneralRe: can works in 64 bitsmemberSelvin3:10 3 Jun '08  
GeneralRe: can works in 64 bitsmemberSelvin21:48 12 Jun '08  
GeneralSource updatememberSelvin2:27 29 May '08  
Generalhow to integrate ExportdllAttribute into my class librarymemberk7_A6:52 28 May '08  
GeneralRe: how to integrate ExportdllAttribute into my class librarymemberSelvin2:08 29 May '08  
GeneralA little occasion in line 21 at the file ExportDllAttribute.cs, that disables export in Cdecl format.memberLesha M.0:47 12 Mar '08  
GeneralProblem: Failed policy check.memberhere_i_am_190020:26 25 Jun '07  
GeneralRe: Problem: Failed policy check.memberprivacy space23:29 23 Aug '07  
GeneralRe: Problem: Failed policy check.memberGurce14:57 15 Jul '08  
QuestionStrong name DLL - failsmemberStefan Vogel6:44 19 Jun '07  
AnswerRe: Strong name DLL - failsmemberSelvin2:14 20 Jun '07  
QuestionUse with DllMain?memberXen3h2:08 21 May '07  
AnswerRe: Use with DllMain?memberSelvin2:38 22 May '07  
GeneralRe: Use with DllMain?memberXen3h2:54 22 May '07  
GeneralRe: Use with DllMain?memberSelvin3:35 22 May '07  
GeneralRe: Use with DllMain?memberXen3h5:30 22 May '07  
GeneralExport method for use by RunDll32.exememberLeo Vildosola2:19 3 Apr '07  
GeneralRe: Export method for use by RunDll32.exememberSelvin4:13 6 Apr '07  
GeneralRe: Export method for use by RunDll32.exememberLeo Vildosola4:42 6 Apr '07  

General General    News News    Question Question    Answer Answer    Joke Joke    Rant Rant    Admin Admin   

PermaLink | Privacy | Terms of Use
Last Updated: 21 Nov 2006
Editor: Deeksha Shenoy
Copyright 2006 by Selvin
Everything else Copyright © CodeProject, 1999-2008
Web12 | Advertise on the Code Project