This week in reply to my post Chris wrote a comment that, he tried out the Helloworld Silverlight from CodePlex site. While he was able to get the WebPart working in the default site, Webpart seems to have problem with the FBA version of the site (Extended one). I just tried out the same example and in my case the extended application I used was not based on Forms but Windows itself. The issue with this is when you extend the web application; new web.config file is copied to the extended application which lacks the entire configuration that SilverLight needs. To solve this issue immediately after you extend the Web Application replace the extended web applications web.config file with the one in the Default site, by this you will have all the setting as in the default site and then you can change the Extended web applications web.config to have FBA / your Provider configured.
You can get the Sample Web.Config file for Silverlight from this post.
Great article on Dual Authentication from Andrew.
Recently when I was working with ASP.NET 3.5 driven SharePoint I got few strange error, to make sure everything is configured properly I crosschecked with the IIS and found that SharePoint application is running ASP.NET 2.0 version,quickily coming to the conclusion that ASP.NET 3.5 is not registered to the IIS. After a quick search I found this article that taught me the truth that
“…… .NET 3.5 is not a standalone framework like v2.0 or v1.1 . It is just an extension of the 2.0 framework. The extension provides developers with new language features like Anonymous Types, Extension Methods, Lambda Expressions and of course LINQ …. and AJAX is now integrated … also you have a few new ASP.NET controls <asp:ListView>, <asp:LinqDataSource>, <asp:DataPager>……“
Recently I was working on a task of converting the SharePoint site running in ASP.NET 2.0 to ASP.NET 3.5. If you are doing the same there is an easier and nice way to do the same. Please follow this link which guides you a kind of automated way to achieve it. Make sure that you include the System.Web.Extensions assembly in the SafeControls.
Also after done with the conversion I tried to code come web Services by using Hand much without intelli-sence help of Visual Studio, when which I encountered an interesting issue in fact a compiler error which says ‘System.Data.DataRowCollection’ does not contain a definition for ‘Cast’ and the best extension method overload ‘System.Data.EnumerableRowCollectionExtensions.Cast<TResult>(System.Data.EnumerableRowCollection)’ has some invalid arguments. Initially I narrowed down it to be some configuration issue, but it was because of missing Namespace. System.Linq By the fact that all the extension methods are defined in the System.Linq Namespace.