C# Modular Application

Welcome to the C# world. Jump in. The water is just fine.

When you structure your project, add folders to your Visual Studio solution for each those areas, so you'll end up with folders for Debtors, Cashbook, Payroll, etc. Each will then get compiled to its own DLL.

Craig Berntson
MCSD, Visual C# MVP,

Hi Craig,

Thanks for welcoming me!

The modules have a GUI. Will they really work if compiled as a DLL? Again friend, I am still navigating the uncharted waters, so my questions may appear quite uninformed, but I must learn. Any helpful information will be highly appreciated.

Benson

No GUI in a DLL was an artificial limitation imposed by VFP. It was there because the DLL libraries didn't have any UI code in them.

There is nothing stopping you from doing it in .Net.

Craig Berntson
MCSD, Visual C# MVP,

I did not know this. New knowledge to me. And this is considered 'good practice'? Thanks again.

Yes, it is considered good practice as it allows you to separate concerns.

Craig Berntson
MCSD, Visual C# MVP,

To elaborate a bit...

If the project needs to be highly modular, you'll probably want to create interfaces that define the pattern that modules need to use. That way the modules can be compiled as DLLs which use the interface, but don't have to know anything else about about the main application beyond whatever hooks you provide it.

Then, once its all done, you can make the main application scan the directory for DLL files, when it finds one, check to see if it is of the interface type that defines modules, and then load it. This way you end up with a system where the modules are now plugins, independent of the main program (and its very easy to simply drop in a new DLL when you need to extend functionality). Plus, it also provides an easy path for other developers to extend your program later on; they don't have to understand how the main applications does things, they just have to know how the subset that lets them interface works.