C# Application Question

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello

I am currently building a small application that uses an Access Database as the backend to store it's data. Currently I have only one EXE that starts the application, what I wanted to know is that there are any resources or info that any one can provide that can help me to maybe break up the program. An example would be to create c# dll's to be used by the program. My idea on doing this is to see if I can bring down the amount of memory the application uses (I will use a profiler later to help me identify the code that may be causing this right now). I want to see if there is something out there that I can use as a 'frame work' so that I get into the habit of writing my applications this way! I just don't want to use one EXE file that grows as I add more features, I want to have a small exe file with other 'helper' files for the application to function properly

Any info you may give me will be greatly appreciated

thanks

Ed P.
 
I don't know if my way is the best but has worked well for me. It allows me
to update my applications without too much re-compile. I create a few dll
projects in the same solution based on what they do (I always set up my
namespaces as "Company" - "Application" - "Component"):

RedCube.NSA.Security: It provides all the security for the app (login,
change passwords, access, etc).
RedCube.NSA.Utilities: Has generic methods like displaying a customer error
messages, about box, splash, etc.)
RedCube.NSA.Database: In charge of connecting to server/database, providing
an open database to calling methods, disconnecting when idle, etc. Sometimes
I call it "Storage" if working with files and not databases. I also tend to
call this "Documents" as in old trusty MFC.
RedCube.NSA.Business: Holds all my business objects that retrieve
information, enforces business rules, etc.
RedCube.NSA.Common: Holds my custom controls, abstract classes, etc.
RedCube.NSA.WinUI: My Windows executable.
RedCube.NSA.WebUI: If it's a web application.

As I said, probably not the best but it's worked pretty well if various
projects.

Eddie Paz

Ed_P. said:
Hello,

I am currently building a small application that uses an Access Database
Click to expand...
as the backend to store it's data. Currently I have only one EXE that
starts the application, what I wanted to know is that there are any
resources or info that any one can provide that can help me to maybe break
up the program. An example would be to create c# dll's to be used by the
program. My idea on doing this is to see if I can bring down the amount of
memory the application uses (I will use a profiler later to help me identify
the code that may be causing this right now). I want to see if there is
something out there that I can use as a 'frame work' so that I get into the
habit of writing my applications this way! I just don't want to use one EXE
file that grows as I add more features, I want to have a small exe file with
other 'helper' files for the application to function properly.
 
Back
Top