How do you organize your projects?

I am switching from Delphi to VS12/C# (or trying) and so the paradigm is new to me.  If I just take the defaults when naming and saving projects and modules I get a confusing, ambiguous and disorganized collection of files.

What is a simple way to name and save that will be organized and not cause problems when a new version of VS comes out?
Kenny HoptonAsked:
Who is Participating?
käµfm³d 👽Connect With a Mentor Commented:
Well your project really shouldn't be affected by new versions of VS. IMO, you would have to worry more about deprecated features rather than your project itself.

As far as naming, I would typically name a project according to its function. If you follow n-tier architectural style, then you would have a library for your business layer, your data access layer, and your user interface layer (and any other pertinent layers). Take a look at some of the libraries within the Framework itself (which can be found in C:\Windows\Microsoft.NET\[version folder]). Look at the names of some of the libraries and you should get a very high level feel of what they do. The same would hold true for your naming.
Kenny HoptonAuthor Commented:
So you don't do anything with folders?  Nothing to indicate versions?  This is where the complexity emerges.
käµfm³d 👽Connect With a Mentor Commented:
Most professional shops maintain some sort of version control software. Team Foundation Server (TFS) is the big name for .NET development. You could also use SVN and I believe GIT, though I have no experience with the latter.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.