|
-
Aug 3rd, 2010, 04:53 PM
#1
Thread Starter
Junior Member
Looking for suggestions
I am thinking about writing a niche market accounting application with several modules (Accounts Payable, Accounts Receivable, G/L, etc) in Visual Basic 2010. The back end database is going to be SQL Server. What I am wondering is would it be best to make this application into 1 single large "exe" file, or into many smaller ones, say one for A/P, one for G/L, etc etc.?
I have never written anything on this scale (in vb anyway, in mainframe languages I have and its all in different files)
-
Aug 3rd, 2010, 10:04 PM
#2
Thread Starter
Junior Member
Re: Looking for suggestions
-
Aug 5th, 2010, 09:57 AM
#3
Lively Member
Re: Looking for suggestions
One exe that references multiple assemblies
I wrote a book  Visual Studio 2008 Programming
Amazon.com / Visual Studio 2008 Programming / By Jamie Plenderleith & Steve Bunn
-
Aug 5th, 2010, 10:03 AM
#4
Re: Looking for suggestions
I'd go with the modular approach to this as well.
-tg
-
Aug 5th, 2010, 10:23 AM
#5
Thread Starter
Junior Member
Re: Looking for suggestions
Thanks for the replies. Excuse my ignorance but could you clarify what you mean by referencing multiple assemblies?
-
Aug 6th, 2010, 02:24 PM
#6
Re: Looking for suggestions
He means, create one class for each functionality (Accounts Payable, Accounts Receivable, G/L, etc) .
The class would get compiled to a separate DLL files.
That's what I understood.
Everything that has a computer in will fail. Everything in your life, from a watch to a car to, you know, a radio, to an iPhone, it will fail if it has a computer in it. They should kill the people who made those things.- 'Woz'
save a blobFileStreamDataTable To Text Filemy blog
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|