While SharePoint 2010 supports .NET 3.5, it uses the .NET 2.0 compiler by default for ASP.NET pages. If you write any UserControls or consume any DLLs in your hosted ASPX pages that utilizes .NET 3.5 features such as the var keyword, extension methods, and LINQ, you’ll get compilation error messages when attempting to access those pages.
To resolve this issue, you can edit the web.config in your site collection’s virtual directory (Usually under \inetpub\wwwroot\wss\virtualdirectories\<site>). Add the following snippet under the configuration element:
<compiler language=”c#;cs;csharp” extension=”.cs” warningLevel=”4″
type=”Microsoft.CSharp.CSharpCodeProvider, System, Version=22.214.171.124,
Have you ever thought to yourself that the development experience in SharePoint is quite frankly a pain? That there are no real best practices or guidance about how to conduct application development or how to use an Application Lifecycle Management (ALM) process?
I was introduced today to the link below on msdn that offers a series of articles whose goal is to define some best practices and offer guidance on how to conduct an ALM process using tools such as Visual Studio and Team Foundation Server.
Most of the articles are still under construction, but this definitely looks like a link to keep handy.
The link is http://msdn.microsoft.com/en-us/sharepoint/cc990283.aspx.