I’ve finally gotten around to starting a CodePlex project for publishing SharePoint features called Trentacular SharePoint 2007 Features. The first contribution to the project should reach a broad audience (within the SharePoint population that is) … an ASP.Net 3.5 Upgrade Feature.
The Feature is naturally scoped to a Web Application and adds ASP.Net 3.5 entries to the particular Web Application’s web.config file. It works for both WSS and MOSS and also supports clean deactivation by iterating through the SPWebConfigModification collection and removing modifications by owner instead of recreating the modifications. All modifications are done through a utility class called SPWebConfigModificationHelper which can be taken advantage of alone if you are writing your own modifications.
Before deciding to write this feature, stuff I tried several others that have been published. Each had its own issues, diagnosis from not supporting clean deactivation to simply just not adding the correct entries. The entries this feature writes were taken from the Visual Studio ASP.Net 3.5 Web.config template.
If you give this Feature a shot, please let me know how it goes.
Hi Jan,
Is this feature still required or has a CU or service pack since included these web.config references? New web apps appear to be getting all the required references but I wanted to be sure.
Thanks,
Paul
SharePoint 2010 now includes the ASP.Net 3.5 Extensions web.config updates, but does not include the C# 3.0 compiler (only needed if you plan to write custom controls having C# 3.0 language features in the markup). Are you using WSS/MOSS (SharePoint 2007) or SharePoint 2010?