March, 2011

Hey everyone – it’s open beta season again in Visual Studio land! (The official announcement is on Jason or Soma ’s blogs.) VS 2010 SP1 is coming out this week. You can download and install the beta starting this Thursday (3/10/11). Or, if you have an MSDN subscription, apparently you can download it today via the MSDN subscriber downloads .   The full list of changes is in the KB release notes here . I see just a few change notes there related to Workflow: XAML support: Workflow files that...

REST is primarily about 2 things, Resources and Representations. If you’ve seen any of my recent talks you’ve probably seen me open Fiddler and how our ContactManager sample supports multiple representations including Form Url Encoded, Xml, Json and yes an Image. I use the image example continually not necessarily because it is exactly what you would do in the real world, but instead to drive home the point that a representation can be anything. Http Resources / services can return anything and are...

Here is the latest in my link-listing series .  Also check out my Best of 2010 Summary for links to 100+ other posts I’ve done in the last year. [I am also now using Twitter for quick updates and to share links. Follow me at: twitter.com/scottgu ] ASP.NET 35 ASP.NET and VS 2010 What’s New Videos : 35 free videos from Joe Stagner that highlight some of the new features that came in ASP.NET 4 and VS 2010. Filling in PDF Forms with ASP.NET and iTextSharp : Nice article by Scott Mitchell on how...

Been a while since our last roundup and since my last blog post for that matter! Fortunately there’s been a bunch of cool stuff going on in the community with our Web APIs that I can point you to. Great to see the community momentum pick up as we cross the 5000 download mark on Codeplex ! Blogs WCF Web API general A new Web for .NET: WCF Web APIs – Ryan Riley talks about the new Web APIs and work he is doing in F# to offer a Sinatra like experience using them. WCF HTTP – Start Using It – Gustavo...

This refers to the previous version of Workflow, but it came up in a recent discussion, so I thought I'd share the relevant points. When developing a Workflow solution that uses persistence and tracking, you may wonder if you should run the scripts for both schemas on the same database, or create separate databases for both. In general, the recommended method is to use a single database, for performance reasons- since both the persistence and tracking components can share a connection, and can...