>>
 

UCanCode's Flow Diagramming Source Code Kit C# Solution Can be found here

First tutorial

    > md C:\learncs
    > cd C:\learncs
    > C:
    

    using System;
  
    public class Hello
    {
        public static void Main()
        {
            Console.WriteLine("Hello C# World :-)");
        }
    }
    

Second tutorial

    > md ..\learncs2
    > cd ..\learncs2
    > notepad hello.cs
    

    using System;
  
    public class Echo
    {
        string myString;
        
        public Echo(string aString)
        {
            myString = aString;
        }
       
        public void Tell()
        {
            Console.WriteLine(myString);
        }
    }
        
    public class Hello
    {
    	public static void Main()
    	{
            Echo h = new Echo("Hello my 1st C# object !");
            h.Tell();
    	}
    }
    

Third tutorial

    using System;
    
    public class Hello
    {
    	public static void Main()
    	{
    	    HelloUtil.Echo h = new HelloUtil.Echo("Hello my 1st C# object !");
            h.Tell();
    	}
    }
    

    using System;
    
    namespace HelloUtil
    {
        public class Echo
        {
            string myString;
            
            public Echo(string aString)
            {
                myString = aString;
            }
            
            public void Tell()
            {
                Console.WriteLine(myString);
            }
        }
    }
    

Now you could compile both in one .exe with
  > csc /nologo /out:hello.exe *.cs
But it's not my intention, no.
Well.
(Have you tried?)
Let's go building a DLL:
  > csc /nologo /t:library /out:echo.dll echo.cs
that's it (dir will confirm).
Now we could use it ...
  > csc /out:hello.exe /r:echo.dll hello.cs
if you typed "hello" it will worked as usual..., but if you delete "echo.dll" the program will now crash: it use the DLL. You could also change Echo.cs, rebuild the DLL and see... that's the advantage of DLL!

You could also put your DLL in the global assembly cache (GAC), and any program would be able to access it, even if the DLL is not in its directory!
to put it in the GAC, I sugest you read MS doc but here are the unexplained step:

1. create your assembly key, create it once and use it for every version. you create it with:
     sn -k myKeyName.snk
   the .snk file should be in your compilation directory (the one where your run csc)
2. create a strong asssembly title by adding in any .cs source file the following directive at top level:

       using System.Reflection;	
       using System.Runtime.CompilerServices;
       [assembly: AssemblyTitle("My Lib Title")]
       [assembly: AssemblyVersion("1.2.3.4")]
       [assembly: AssemblyKeyFile("myKeyName.snk")]
       

3. now add it to the GAC:
     > gacutil.exe /if myLib.dll

By the way, did I tell you ? when I referenced the hello.dll while compiling, remember? csc /out:hello.exe /r:echo.dll hello.cs, it could have been any assembly, even a .exe !!!

Fourth tutorial

    #include <stdio.h>
    
    #define DLLOBJECT __declspec(dllexport)
    
    DLLOBJECT void writeln(char* s)
    {
        printf("%s\n", s);
    }
    

    using System;
    using System.Runtime.InteropServices;
    
    namespace HelloUtil
    {
        public class Echo
        {
            [DllImport("echo.native.dll", CallingConvention=CallingConvention.Cdecl)]
            static extern void writeln(string s);
            
            string myString;
            
            public Echo(string aString)
            {
                myString = aString;
            }
            
            public void Tell()
            {
                writeln(myString);
            }
        }
    }
    

    using System;
    using HelloUtil;
    
    public class Hello
    {
    	public static void Main()
    	{
    		Echo h = new Echo("Hello my 1st interop code !");
    		h.Tell();
    	}
    }
    

And now let's compile this!

    > csc /nologo /t:library /out:echo.dll echo.cs
    > csc /nologo /out:hello.exe /r:echo.dll hello.cs 
    > 
    > rem "if the following line don't work, read bellow.."
    > gcc -shared -o echo.native.dll echo.c
    > strip echo.native.dll
    

Now I should admit I didn't tell you all the truth. echo.dll and echo.native.dll are not the same kind of DLL. It's not just the language (C / C#) the C one is a plain executable full of, probably, x86 instruction, whereas the C# one is what MS call a portable executable.. anyway they are different.
If you install echo.dll in the GAC it wont work because it won't find echo.native.dll except if you put in into the PATH (like C:\Windows\System32).
In the same manner when you add the reference in VS.NET echo.native.dll is overlooked and your program won't work....
So either put the native one in your path or copy it in the debug/release directory of VS.NET.
Or do everything by hand (makefile? build.bat?) and put all your dll in you build directory, and everything work fine..

And now..

Now you are ready to understand, I could tell you all the truth:
csgl.dll is a C# assembly and csgl.native.dll is just a dll compiled by GCC, upon which csgl.dll depends...

Get Business Card / Label Print Component C++ Source Codes

Add proto - logic diagram displays to your Java, C++, and .NET applications, for the desktop and rich internet applications.

UML Diagram Component / Drawing C++ Source Code Solution from ucancode, it will save you 50% - 80% time for building any UML based application.

VC++ XML Read and Write Article: C++ Source Code  for Creating and Processing XML documents