http://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspxknowledgeexchange Releases Rss Descriptionhttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35837<div class="wikidoc">In the last article we removed the dependency that our front end and middle tier code had on our data access layer. This provided us with an application that has no ties to the data access technology that is used to connect to the surrounding infrastructure. This made the application more flexible in that the data access code and repositories can be swapped out for something new. The codebase howe</div><div class="ClearBoth"></div>asiemerFri, 13 Nov 2009 06:05:14 GMTCreated Release: DNS 13 - Three Tiers To MVC - Dependency Injection (Nov 12, 2009) 20091113060514Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35837<div>In the last article we removed the dependency that our front end and middle tier code had on our data access layer. This provided us with an application that has no ties to the data access technology that is used to connect to the surrounding infrastructure. This made the application more flexible in that the data access code and repositories can be swapped out for something new. The codebase howe</div><div></div>Fri, 13 Nov 2009 06:05:14 GMTReleased: DNS 13 - Three Tiers To MVC - Dependency Injection (Nov 12, 2009) 20091113060514Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35271<div class="wikidoc">In this article we will focus on less of the structural issues and instead work on removing our dependency on LINQ to SQL. We will achieve this by employing an object to object mapping tool called AutoMapper. We will create plain old CLR objects (POCO for short) that we can then map our LINQ to SQL objects too. We will then refactor our application to be dependent upon our internal POCO objects instead of the LINQ to SQL generated objects. This will effectively allow our ORM choice to be independent of our code base which will allow us to swap LINQ to SQL out for Entity Framework 4.0 when it comes out next year!</div><div class="ClearBoth"></div>asiemerTue, 03 Nov 2009 05:20:12 GMTUpdated Release: DNS 12-Three Tiers to MVC - Reversing Dependencies (Nov 01, 2009) 20091103052012Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35271<div>In this article we will focus on less of the structural issues and instead work on removing our dependency on LINQ to SQL. We will achieve this by employing an object to object mapping tool called AutoMapper. We will create plain old CLR objects (POCO for short) that we can then map our LINQ to SQL objects too. We will then refactor our application to be dependent upon our internal POCO objects instead of the LINQ to SQL generated objects. This will effectively allow our ORM choice to be independent of our code base which will allow us to swap LINQ to SQL out for Entity Framework 4.0 when it comes out next year!</div><div></div>Tue, 03 Nov 2009 05:20:12 GMTReleased: DNS 12-Three Tiers to MVC - Reversing Dependencies (Nov 01, 2009) 20091103052012Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35271<div class="wikidoc">In this article we will focus on less of the structural issues and instead work on removing our dependency on LINQ to SQL. We will achieve this by employing an object to object mapping tool called AutoMapper. We will create plain old CLR objects (POCO for short) that we can then map our LINQ to SQL objects too. We will then refactor our application to be dependent upon our internal POCO objects instead of the LINQ to SQL generated objects. This will effectively allow our ORM choice to be independent of our code base which will allow us to swap LINQ to SQL out for Entity Framework 4.0 when it comes out next year!</div><div class="ClearBoth"></div>asiemerMon, 02 Nov 2009 03:16:17 GMTCreated Release: DNS 12-Three Tiers to MVC - Reversing Dependencies (Nov 01, 2009) 20091102031617Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=35271<div>In this article we will focus on less of the structural issues and instead work on removing our dependency on LINQ to SQL. We will achieve this by employing an object to object mapping tool called AutoMapper. We will create plain old CLR objects (POCO for short) that we can then map our LINQ to SQL objects too. We will then refactor our application to be dependent upon our internal POCO objects instead of the LINQ to SQL generated objects. This will effectively allow our ORM choice to be independent of our code base which will allow us to swap LINQ to SQL out for Entity Framework 4.0 when it comes out next year!</div><div></div>Mon, 02 Nov 2009 03:16:17 GMTReleased: DNS 12-Three Tiers to MVC - Reversing Dependencies (Nov 01, 2009) 20091102031617Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34302<div class="wikidoc">In this article we will take the next step in improving this code by further elevating our logical tiers to physical tiers. This simply means that we will create separate assemblies for each of the separate tiers. By the end of this article we will have our web project, a business layer project, domain project, and a data access project. As we will see shortly this will alleviate some of the pains that we observed in our last article. But it should serve to surface a few other dependencies that we have not really had a good view of yet.</div><div class="ClearBoth"></div>asiemerTue, 27 Oct 2009 04:07:23 GMTUpdated Release: DNS 11 - Three Tiers to MVC - Physical Seperation (Oct 11, 2009) 20091027040723Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34302<div>In this article we will take the next step in improving this code by further elevating our logical tiers to physical tiers. This simply means that we will create separate assemblies for each of the separate tiers. By the end of this article we will have our web project, a business layer project, domain project, and a data access project. As we will see shortly this will alleviate some of the pains that we observed in our last article. But it should serve to surface a few other dependencies that we have not really had a good view of yet.</div><div></div>Tue, 27 Oct 2009 04:07:23 GMTReleased: DNS 11 - Three Tiers to MVC - Physical Seperation (Oct 11, 2009) 20091027040723Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34301<div class="wikidoc">In this article we will start to address some of the flaws in our original design. The first step will be to refactor towards logical separation of our code. Then we can analyze the code to see what the remaining issues are. Then we will analyze the pros and cons of this design.</div><div class="ClearBoth"></div>asiemerTue, 27 Oct 2009 03:39:32 GMTUpdated Release: DNS 10 - Three Tiers to MVC - Logical Seperation (Oct 11, 2009) 20091027033932Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34301<div>In this article we will start to address some of the flaws in our original design. The first step will be to refactor towards logical separation of our code. Then we can analyze the code to see what the remaining issues are. Then we will analyze the pros and cons of this design.</div><div></div>Tue, 27 Oct 2009 03:39:32 GMTReleased: DNS 10 - Three Tiers to MVC - Logical Seperation (Oct 11, 2009) 20091027033932Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34301<div class="wikidoc">In this article we will start to address some of the flaws in our original design. The first step will be to refactor towards logical separation of our code. Then we can analyze the code to see what the remaining issues are. Then we will analyze the pros and cons of this design.</div><div class="ClearBoth"></div>asiemerMon, 12 Oct 2009 01:57:17 GMTUpdated Release: DNS 10 - Three Tiers to MVC - Logical Seperation (Oct 11, 2009) 20091012015717Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34301<div>In this article we will start to address some of the flaws in our original design. The first step will be to refactor towards logical separation of our code. Then we can analyze the code to see what the remaining issues are. Then we will analyze the pros and cons of this design.</div><div></div>Mon, 12 Oct 2009 01:57:17 GMTReleased: DNS 10 - Three Tiers to MVC - Logical Seperation (Oct 11, 2009) 20091012015717Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34301<div class="wikidoc">In this article we will start to address some of the flaws in our original design. The first step will be to refactor towards logical separation of our code. Then we can analyze the code to see what the remaining issues are. Then we will analyze the pros and cons of this design.</div><div class="ClearBoth"></div>asiemerMon, 12 Oct 2009 01:35:15 GMTCreated Release: DNS 10 - Three Tiers to MVC - Logical Seperation 20091012013515Ahttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34251<div class="wikidoc">This release includes the sketchflow project.</div><div class="ClearBoth"></div>asiemerSun, 11 Oct 2009 23:48:23 GMTUpdated Release: DNS 7 - 8 - Sitemap and Wireframe with SketchFlow (Oct 10, 2009) 20091011114823Phttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34251<div>This release includes the sketchflow project.</div><div></div>Sun, 11 Oct 2009 23:48:23 GMTReleased: DNS 7 - 8 - Sitemap and Wireframe with SketchFlow (Oct 10, 2009) 20091011114823Phttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34261<div class="wikidoc">In the last article we took a look at some team collaboration aspects of SketchFlow in the form of getting feedback from the users of our prototype. Then we built a reusable component for our header and navigation controls that all of the screens in our prototype project could use. Once we had a header through out our entire project we then implemented a navigation in our top and primary navigation buttons. Then we created the guts of a couple of pages to show how easy it was to quickly mock up a page. Finally we discussed managing the various states of a page with SketchFlow’s state management tools.<br /><br />With our prototype concepts demonstrated we can start to build our application while discussing some architectural concepts. In this article series we are going to discuss some architectural concepts. The plan is to start off creating the most simple project possible – a web page that dips directly into the database to get a list of questions for our Knowledge Exchange. Once we have that working we will walk through several refactorings of our code to slowly get it to a point that it is ultimately flexible and scalable. With each type of refactoring we will discuss the pros and cons involved with that decision. By the end of this mini-series we should have a very strong, flexible, and scalable baseline to start building our Knowledge Exchange on top of. More important you will know what someone means when they talk about a tiered application and be able to pick apart the various forms of this very generic term!</div><div class="ClearBoth"></div>asiemerSun, 11 Oct 2009 19:42:46 GMTUpdated Release: DNS 9 - Three Tiers to MVC - Hooray - Simple (Oct 10, 2009) 20091011074246Phttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34261<div>In the last article we took a look at some team collaboration aspects of SketchFlow in the form of getting feedback from the users of our prototype. Then we built a reusable component for our header and navigation controls that all of the screens in our prototype project could use. Once we had a header through out our entire project we then implemented a navigation in our top and primary navigation buttons. Then we created the guts of a couple of pages to show how easy it was to quickly mock up a page. Finally we discussed managing the various states of a page with SketchFlow’s state management tools.<br><br>With our prototype concepts demonstrated we can start to build our application while discussing some architectural concepts. In this article series we are going to discuss some architectural concepts. The plan is to start off creating the most simple project possible – a web page that dips directly into the database to get a list of questions for our Knowledge Exchange. Once we have that working we will walk through several refactorings of our code to slowly get it to a point that it is ultimately flexible and scalable. With each type of refactoring we will discuss the pros and cons involved with that decision. By the end of this mini-series we should have a very strong, flexible, and scalable baseline to start building our Knowledge Exchange on top of. More important you will know what someone means when they talk about a tiered application and be able to pick apart the various forms of this very generic term!</div><div></div>Sun, 11 Oct 2009 19:42:46 GMTReleased: DNS 9 - Three Tiers to MVC - Hooray - Simple (Oct 10, 2009) 20091011074246Phttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34251<div class="wikidoc">This release includes the sketchflow project.</div><div class="ClearBoth"></div>asiemerSun, 11 Oct 2009 18:44:49 GMTUpdated Release: DNS 7 - 8 - Sitemap and Wireframe with SketchFlow (Oct 10, 2009) 20091011064449Phttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=34251<div>This release includes the sketchflow project.</div><div></div>Sun, 11 Oct 2009 18:44:49 GMTReleased: DNS 7 - 8 - Sitemap and Wireframe with SketchFlow (Oct 10, 2009) 20091011064449Phttp://knowledgeexchange.codeplex.com/Release/ProjectReleases.aspx?ReleaseId=31994<div class="wikidoc">In this article we will take an additional step in the completion of our local development environment by adding various forms of build automation. For build automation I use NAnt as it is well supported, easy to customize (as we will see), and works with many other tools that we may need to integrate with later. We will specifically tackle first time environment initialization, the compilation of all the projects in our solution, unit testing our code, database integration, and environment re-initialization. <br /><br />http://dotnetslackers.com/articles/aspnet/Building-a-StackOverflow-inspired-Knowledge-Exchange-Build-automation-with-NAnt.aspx</div><div class="ClearBoth"></div>asiemerSun, 11 Oct 2009 18:28:45 GMTUpdated Release: DNS 3 - Build automation with NAnt (Aug 25, 2009) 20091011062845P