SharePoint 2007 and the Thin .NET 3.5 Development Model
Merge your SharePoint development with WCF to work around some of SharePoint 2007's problems and enable the thin .NET development model.
by Sahil Malik
January 5, 2009
hile flying back home over the Atlantic, I thought about how much better developing for SharePoint has become after the introduction of .NET 3.5. I have repeatedly insisted that one of the reasons behind SharePoint 2007's huge success is the application of ASP.NET 2.0 concepts to SharePoint.
This article provides a brief introduction to the specific improvements that .NET 3.5 brings to the SharePoint 2007 platform, and how those have improved my development life.
I was just one of many scratching their heads when Soma announced that Indigo, Avalon, etc. would be named .NET 3.5. I've said it before, and I'll say it again: I am convinced that there is a department at Microsoft whose sole job is to give bad names to good products. Count me firmly entrenched in the camp of people who feel .NET 3.5 is a misnomer. .NET 3.5 is based on CLR 2.0, so it is really .NET 2.0 with a whole bunch on top. But, history cannot be rewritten, so we're stuck with that name.
It's quick, easy and you get access to all the articles on DevX.
This registration/login is to allow you to read articles on devx.com. Already a member?
To become a member of DevX.com create your Member Profile by completing the form below. Membership is free!
hile flying back home over the Atlantic, I thought about how much better developing for SharePoint has become after the introduction of .NET 3.5. I have repeatedly insisted that one of the reasons behind SharePoint 2007's huge success is the application of ASP.NET 2.0 concepts to SharePoint.
