RIAServices.Toolkit.All - Includes all of the above NuGet packages except ViewModel - as that's the only Silverlight-targeted package and including it was causing problems for folks trying to apply the Toolkit.All package to a .NET project.

What’s the difference?

We have both the RiaServicesToolkit.msi and the NuGet packages, so what’s the difference? Generally speaking, there is no difference other than the ship vehicles. We’re starting to favor NuGet over the Toolkit MSI for distributing our Toolkit components. I would love to hear your thoughts on the pros/cons of each though! With tonight’s releases, everything available via NuGet is also available as a component within the Toolkit MSI.

There are some MSI features that are not available via NuGet though:

Linq to Sql support (LinqToSqlDomainService) - This feature requires the addition of a registry key in order for the Domain Service Wizard (Add New Item… Domain Service) to recognize a Linq to Sql DataContext. If there is demand for adding a NuGet package for this, we could do it and add the registry key using an Install.ps1 script, but I’d feel awfully dirty doing that.

ASP.NET DomainDataSource and DomainValidator - These features require VS integration through design-time components, and there presently isn’t a good way to install these bits through NuGet.

Otherwise, tonight’s release gets the Toolkit and the NuGet packages in sync.

What was updated?

There are two note-worthy changes in tonight’s release:

EntityFramework 4.1 support was added to the Toolkit via the Microsoft.ServiceModel.DomainServices.EntityFramework assembly. Previously, this was only available via the RIAServices.EntityFramework NuGet package, but it’s now rolled into the Toolkit MSI as well.

JavaScript/jQuery client (RIA/JS) updates. These updates are in both the Toolkit MSI and the RIAServices.jQuery NuGet package. When we first released this preview (and yes, it’s still in early preview form), it only worked with jQuery 1.4.4. Now it works with jQuery 1.5.1+ (including 1.6.1). There has been quite a bit of code refactoring and preparation for many new features.

There were also quite a few bug fixes. We fixed bugs in our EF Code First support, in the ViewModel features, and other various places. Nothing comes to mind as being very noteworthy though.

Lastly, we also updated the NuGet packages to include and require a license acceptance upon reference into your project. Exciting, huh?

I do think the RIA/JS support for the latest version of jQuery is worth grabbing the new bits for. I know many of you were hit by our 1.4.4-specific targeting, so you should now be unblocked. We’ve been working very closely with the jQuery team to ensure that the data observability model we use is jQuery-friendly (of not endorsed), and there was a lot of work put into RIA/JS to get us poised for developing more features and richness into the client while ensuring we fit nicely into the jQuery ecosystem.

Is this for SP1 or SP2?

The updated Toolkit and NuGet packages work with both WCF RIA Services V1.0 SP1 and SP2, with one exception: the JavaScript client (RIA/JS). RIA/JS requires SP2.

Forums

As always, if you have questions or problems, I recommend you jump over to the forums.

I have one question: Is the DomainCollectionView ever going to be compatible with the DataForm?Since at the moment the DCV gives an exception when adding a new item through the DataForm when the view is sorted.

Are you using the DataForm and the DataGrid together, bound to the same view? If so, unfortunately that can lead to some issues where the two controls don't play nicely together as they are both trying to manage currency on the view.

I chatted with Kyle McClellan and he suggested:

"I think the solution is that you must have separate instances of the DCV/ICV for the DataGrid and DataForm and keep the two in sync via a SelectedItem binding. I think I did something like this in my SLTV sample.

"For right now, you need a separate instance for each. Also, I think you could successfully bind the DataForm to DCV.SourceCollection to fix the problem and avoid multiple ICV instances (at least avoiding explicitly declaring them)."

Jeff, I used the scaffolding.I got LS to see the service it just doesn't build correctly.. hate to double post but here are the errors:Error 1 The type 'SLCLCAData.Services.ControllersAssistantDomainService' cannot be used as type parameter 'TServiceContext' in the generic type or method 'Microsoft.LightSwitch.ServerGenerated.Implementation.RiaDataServiceImplementation<TContext,TServiceContext>'. There is no implicit reference conversion from 'SLCLCAData.Services.ControllersAssistantDomainService' to 'System.ServiceModel.DomainServices.Server.DomainService'. D:\SourceCode\New folder\HSProjects\Old\WcfServiceLibrary1\CompanyEditorWCF\ServerGenerated\GeneratedArtifacts\DataServiceImplementation.cs 99 18 ServerGenerated

Error 2 The type 'System.ServiceModel.DomainServices.EntityFramework.DbDomainService`1<T0>' is defined in an assembly that is not referenced. You must add a reference to assembly 'Microsoft.ServiceModel.DomainServices.EntityFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'. D:\SourceCode\New folder\HSProjects\Old\WcfServiceLibrary1\CompanyEditorWCF\ServerGenerated\GeneratedArtifacts\DataServiceImplementation.cs 99 18 ServerGenerated