Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unrecognized attribute 'multipleSiteBindingsEnabled'. Note that attribute names are case-sensitive.
Source Error:

Line 105:  -->
Line 106:	<system.serviceModel>
Line 107:		<serviceHostingEnvironment multipleSiteBindingsEnabled="true" />
Line 108:  <services>
Line 109:			<service behaviorConfiguration="RFID.Server.WCF.Service1Behavior" 
name="RFID.Server.WCF.Service1">

Source File: C:\inetpub\web\services.test.\RFIDServer\web.config    Line: 107

---

Version Information: Microsoft .NET Framework Version:4.0.21006; ASP.NET Version:4.0.21006.1

---

Received the above error message when executing a WCF service on a test server.  The WCF service was compiled with .NET  4.0 RC and the test server only had .NET 4.0 Beta 2 installed.  The fix was easy.  Install .NET 4.0 RC full runtime on the test server and it worked.

Update:  Good news!  Microsoft has verified that in the RTM build this bug has been resolved.  Much thanks to Go-Live support for taking this issue on and validating the issue is resolved.

From VS2010 Beta 2 to VS2010 RC we lost the ability to choose the data type ObservableCollection when configuring a service reference in a Silverlight application.  I am going to use this blog post to chronicle my discussion with Microsoft Go-Live support about this functionality change.

---

This may be a user education issue but the difference is significant and affects all of the production projects we currently have for Visual Studio 2010 Beta 2.

Today we upgraded 3 of our developer machines from Visual Studio 2010 Beta 2 to the Visual Studio 2010 RC.  In beta 2 when adding a Service Reference to a Silverlight 3 application we were given the option to choose a collection type of: System.Collections.ObjectModel.ObservableCollection in the Collection type drop down box.

Now in the release candidate we are no longer given the option to choose ObservableCollection.  Instead the dropdown offers ( Custom ), Array, Generic List (and another).  This presents us with several issues.  Existing Beta 2 code can no longer update service references without converting all return types from Array[] or List<> to an ObservableCollection. 

For Silverlight applications this is pretty major as we pass Generic Lists from our WCF service and heavily relied on the ability for the WCF Proxy class to deserialize the list into an ObservableCollection since these are bindable directly to our Silverlight grids.

Please advise.  Is this the way this will work in production or is it possible to patch the RC to provide this functionality once again.

Please feel free to call me tomorrow ( 2/10/2010 ) from 9AM EST to 8PM EST to discuss if you need more information.  It has been a while since I used Visual Studio 2008, but I am pretty sure that VS 2008 also provided the ObservableCollection collection type option when configuring a service reference.

To verify the Beta 2 vs. RC functionality difference I tested this against the same exact WCF service in both B2 and RC.