Charlotte Foust
cfoust at infostatsystems.com
Wed Nov 18 10:12:41 CST 2009
Think of the solution as the application. The projects within the solution can be shared with other applications. We use the projects primarily to group parts of our apps, like UI, Reports, Data, Configuration, Security, etc., but it really is up to the architect of the app. Charlotte Foust -----Original Message----- From: dba-vb-bounces at databaseadvisors.com [mailto:dba-vb-bounces at databaseadvisors.com] On Behalf Of jwcolby Sent: Wednesday, November 18, 2009 5:07 AM To: VBA Subject: [dba-VB] Projects vs Solutions I am hazy on how things are organized in .Net once you start building pieces of code. What is a project, what is a solution and how are they tied together. My role for the "DBFH" client involves lots of different tasks, for which there will be many different pieces. I would hope to tie the pieces together in one big application. For example I just wrote the little applet to cleanup CSV files, which will have to be used again. I do exports to Accuzip, imports from Accuzip, these two are closely related obviously. I build orders. I have to export data from tables for processing by external processing houses, which involves a very similar export / zip / FTP process. So as I build these processes in C#, how are they physically organized on the disk, and how are they tied back together into one program. From what I am reading, a Solution is the big picture, a Project is a small part of the Solution. But when I open VS2008 there is no "create a solution" or at least I don't see one. So how does one create a solution, and then look at just one project at a time inside of that solution? -- John W. Colby www.ColbyConsulting.com _______________________________________________ dba-VB mailing list dba-VB at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-vb http://www.databaseadvisors.com