Structure and Guidance for Organizing Applications within Visual Studio

Filing CabinetVisual Studio is an outstanding tool when it comes to building applications on the .Net Framework. It can be confusing for users when trying to initialize a new software deliverable though. For example, how do you name your projects? Where do you put third party assemblies so they can be re-used? How do you set things up for an n-tier architecture? And the list goes on. I've given various talks throughout the US and it never fails that I end up in a conversation with multiple people on what are the best ways to organize projects within Visual Studio. This session should answer these questions and provide some proven guidance that works. In this session we'll cover some best practices on how to organize your projects and solutions. We'll also look at some tricks and guidance on how to map your folder structure to your namespaces. During the session we are going to build a new application from scratch and cover how to initially incorporate an n-tier design when initializing your project. Even if you are an experienced .Net developer this is one session you will not want to miss!

This topic was presented by Keith Elder at the Tuesday, November 23, 2010 meeting.

This web site uses Kentico CMS, the content management system for ASP.NET developers.