Thursday, October 19, 2006

Partial classes

The new Partial keyword was introduced in .NET2.0 for both VB2005 and C#.

In a nutshell , partial classes mean that your class definition can be split into multiple physical files. Logically, partial classes do not make any difference to the compiler. At compile time it simply groups all the various partial classes and treats them as a single entity.

An awesome benefit of partial classes is that they allow a clean separation of business logic and the user interface (code generated by the visual studio designer).

The UI code can be hidden from the developer who normally doesnt need to access it anyways.

Partial classes also make debugging easier because of the partitioned classes. This is great for large develoment teams.

--Partial Class Default_aspx

--End Class

Debugging in 2005

By default the web.config file is not added to the web project.

For debugging you need the web.config file. Its found in the "Visual Studio installed templates".

Using IIS with ASP.NET in 2005

You will need to install IIS before you install Visual Studio 2005.

XP by default does not install IIS, so you will need to use the "Add or Remove Programs" and add it yourself.

If you have installed Visual Studio 2005 allready fear not you can still get them working. You need to associate IIS with ASP.NET. You can do this by using aspnet_regiis utility (located in C:\Windows\Microsoft.NET\Framework\) with the -i option.

------- aspnet_regiis -i

ASP.NET 2.0

Microsoft made some major improvements based on feedback from millions of people and the companies own experience.

One of the aims of the new version is to considerably reduce the amount of code you need to perform common web site tasks (by up to 70%).

There are alot of new features like cross page posting and client side scripts, as well as major improvements to the page framework and new services and api's.