It appears that the History that is saved in .NET 3.5 sp1 beta1 is encoded by default and not human readable. I haven't figured out how secure it is.
When you encode the parameters to save the page state, you can't use complex objects. You have to save strings or nulls. Complex objects can't be saved out. You'll need to enable history on the scriptmanager by setting the EnableHistory. This property...
Subscribe to everything . Original Url: http://aspnetpodcast.com/CS11/blogs/asp.net_podcast/archive/2008/05/31/asp-net-podcast-show-114-ado-net-data-services-in-net-3-5-service-pack-1-beta1-with-asp-net-ajax.aspx Subscribe to WMV . Subscribe to M4V for...
I started working on an example using the ADO.NET Data Services (formerly Astoria) in .NET 3.5 SP!. ADO.NET Data Services uses the Entity Framework to expose data to clients in a restful manner. Its ideally suited to data access over ajax clients. For...
I've started a new tag on my blog about .NET 3.5 SP1 features as I write some examples up on them. http://morewally.com/cs/blogs/wallym/archive/tags/.NET+3.5+SP1/default.aspx. This tag will have all of my posts about new features in .NET 3.5 SP1 along...