There is no code that has to be in it. But a dll is context limited I believe.
Start a new solution put two projects in it. Make a simple startup program and mark as the startup project. The as a separate project create a class library project. Instantiate the DLL in the project. Create a public method in the DLL and call it from the startup program.
That too is easy start a new project of the type Class library. Add your code. Wrap it in a Namespace and then build it. Be aware that a dll is a slightly different environment than a process and does not have accesses to all classes that an executable does.
Joining code
Alex21
helpmeplz
I modified what I said. You may want to take take a look at it. Good Luck!
Vasic
Not in the same class or in the same project
...
However you can have a VB project and a C# project in the same solution
anvaka
That really simple. Include the dll as a reference. That's all you have to do.
Peter paterson
You can also have a C# or C++ DLL with a VB project or vice versa.
DMAN is an expert, expert, expert but because of this ability, I would say it's not as hard as he makes it sound.
ivanbolcina
There is no code that has to be in it. But a dll is context limited I believe.
Start a new solution put two projects in it. Make a simple startup program and mark as the startup project. The as a separate project create a class library project. Instantiate the DLL in the project. Create a public method in the DLL and call it from the startup program.
Bryce Beagley
Ohhh How do you make DLL's
That too is easy start a new project of the type Class library. Add your code. Wrap it in a Namespace and then build it. Be aware that a dll is a slightly different environment than a process and does not have accesses to all classes that an executable does.
Scuzzy
BrentB
Sen_p_kumar
Is there any particular code that HAS to be in it, or can it be like an application and have what you like