Question about organization
-
I've been coding in C# for a few months now and one thing that my books never mention is how I should organize my projects in Visual Studio. For instance, on my current project I made an Mp3 player that uses the Speech API to take commands. Should I make 3 seperate projects in VS, one for all the forms (windows app), one for the Speech Code (class library), and one for the mp3 code (class library)? Or should I have just made one project and put all the code in seperate files? I'm sure there isnt one answer for this, and alot of it comes down to personal preference, but any tips would be much appreciated :-D
-
I've been coding in C# for a few months now and one thing that my books never mention is how I should organize my projects in Visual Studio. For instance, on my current project I made an Mp3 player that uses the Speech API to take commands. Should I make 3 seperate projects in VS, one for all the forms (windows app), one for the Speech Code (class library), and one for the mp3 code (class library)? Or should I have just made one project and put all the code in seperate files? I'm sure there isnt one answer for this, and alot of it comes down to personal preference, but any tips would be much appreciated :-D
Are there components in your MP3 app that you could use in other applications too? If so, maybe start by pulling that code into a separate assembly. Also if you are making enterprise server apps, it's probably a good idea to logically break up your solution into smaller components to facilitate a physically-tiered design. Cheers, Simon "The day I swan around in expensive suits is the day I hope someone puts a bullet in my head.", Chris Carter.
my svg article