The RIA Services team published the August 2011 edition of the Toolkit tonight. We also refreshed all of our NuGet packages:
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.
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?
As always, if you have questions or problems, I recommend you jump over to the forums.