Now the Visual Studio® 2008 Web Deployment Projects - RTW is released. This version of the Web Deployment Projects add-in is a 2008 version of the Web Deployment Projects for Visual Studio 2005.
With the deployment projects add-in you can control the deployment of your web Application easily. You configure it once and with the click of a button you can get a precompliled version of your application.
It really is a XML (project) file, containing the configuration for all your builds (debug, test, release or whatever). In combination with the Web Setup Project (you can make the Web Deployment Project the source for your Web Setup) it is really easy to create Setups for your Web Application. 

Download it here:

Henry Cordes
My thoughts exactly...

Published 26/01/2008 by Henry in ASP.NET

While I changed the bloggingengine for this blog from dasBlog to subText some time ago (because I wanted SQL server support instead of XML Files), a fellow developer pointed me to

My main reason for wanting to change this fast again is that in my opinion is the best option at this moment in time. It provides XML and SQL Server support through the provider model, so a new datasource is easily integrated. I think because it has not been around that long it's foundation is pure ASP.NET 2.0. has learned from the mistakes that dasBlog, subText etc. have made.
In software development projects sooner or later we always come for the choice: 'Are we going on on this path, or are we going to built from scratch?'. I think that is a good example that it sometimes can be rewarding to start all over.

Anyway I moved to so now I have tag support and a new layout once more. is available on Codeplex.

Henry Cordes
My thoughts exactly...

Microsoft Press have just released an e-book on Visual Studio 2008 technologies and are giving it away for free. The e-book includes excerpts from three recent book releases and provides a wealth of information and insights from top experts:

Look here

Henry Cordes
My thoughts exactly...

ASP.NET MVC Framework

Published 27/10/2007 by Henry in ASP.NET | Patterns

On Scott Guthrie's blog I saw that there is going to be a framework to build ASP.Net applications using the Model View Controller pattern.

What is the Model View Controller Pattern?
The MVC design pattern provides the ability to vary different software components separately. The pattern improves the software robustness and reusability.
The MVC pattern helps the software designer to fulfill the object-oriented design principles, such as the Open Closed Principle(OCP).
The idea of the OCP is that developers must decide early on in the analysis or design phase which parts of the system will be expanded later and which will stay fixed.
According to the OCP principle, the design is extended by adding new code and classes by inheriting existing base classes rather than modifying the existing ones.
Completed and tested code is declared closed, and it is never modified.

Classic design pattern Model View Controller
  • Model: Contains and manipulates the data in the program.  These are the components of the application that are responsible for maintaining state.  Often this state is persisted inside a database
  • View: defines how the data of the model is presented to the user; the view forwards received commands and requests to the controller. These are the components responsible for displaying the application's user interface. 
  • Controller:Defines how the user interface reacts to received commands and requests. These are the components responsible for handling end user interaction, manipulating the model, and ultimately choosing a view to render to display UI.  In a MVC application the view is only about displaying information - it is the controller that handles and responds to user input and interaction.

The idea is that the Presentation layer (GUI) easily can be switched from for example an ASP.Net web user interface for a windows Forms user interface.
The discussion if this is practical and will be used in real world applications always comes up when discussing this pattern.
When we switch the UI for a Unit test framework, this discussion is almost always turned over in favor for the pattern, because (Unit)testing ASP.Net Webpages can be quite cumbersome at times.
So just for the sake of (unit) testing our code alone this pattern can really add value to our work as developers.
The maintainability of the code should benefit also, because all the layers of our application are really separated and encapsulated.

The ASP.NET MVC Framework will be fully integrated with ASP.NET, which means it supports existing ASP.NET features like forms/windows authentication, URL authorization, membership/roles, output and data caching, session/profile state management, health monitoring, configuration system, the provider architecture, etc.
It will be pluggable and extensible for example: you can optionally plug-in your own view engine, routing policy, parameter serialization, etc. 
It also supports IOC container models (Windsor, Spring.Net, NHibernate) for using existing dependency injection.
You can unit test the application without having to run the Controllers within an ASP.NET process (making unit testing fast).
You can use any unit testing framework you want to do testing ( NUnit, MBUnit, MS Test).

I really am interested and will try to follow this, frankly I can't wait to try out a CTP.

Henry Cordes
My thoughts exactly...

Microsoft ASP.NET AJAX version 1.0 Beta Released

'ATLAS', Microsoft's AJAX Framework, has changed names, the codename 'ATLAS' is no longer used.
Instead Microsoft ASP.NET AJAX is the official name. The 1.0 Beta version is now released. Download from here
ASP.NET AJAX is a free framework for creating client-centric, interactive Web applications that work across many popular browsers and on any server platform.

More information can be found here:
Microsoft claims the AJAX framework is platform independent. In fact I quote: 'The Microsoft AJAX Library is a standalone collection of the standards-based Javascript classes included in ASP.NET AJAX. It’s supported by most popular browsers and can be used to build client-centric Web applications that integrate with any backend data provider.'

There is a migration guide in case you already implemented one of the ATLAS Beta's or the CTP that was released not that long ago. This guide is available here.
Read the Changes between the ASP.NET AJAX (“Atlas”) CTP and the v1.0 Beta Release whitepaper which is also available as a Word document and a PDF document.

Download  ASP.NET AJAX v1.0 BETA Get involved in ASP.NET AJAX forums destination-videos.gif

Henry Cordes
My thoughts exactly...