After reading this interesting article by Pablo Castro, I have to assume that the real purpose of using Async Execution is for specific use-cases when you need to fire off multiple concurrent queries in service situations (e.g. ASP.NET, Web Services or Windows Services).
Chris Sells asked me today if there was a re-usable connection string user interface that I knew of. I'd heard that you could use the dialog from Visual Studio, but I had to dig in and remember how. I've put together this quick and dirty example for downloading.
Since my announcement last year that there would not be an update to my book ("Pragmatic ADO.NET") to show the changes in ADO.NET 2.0, I have been asked what book I would recommend. I have scoured the ADO.NET 2.0 books and finally have a firm recommendation:
I was having a chat with David Sceppa about TableAdapters recently when he mentioned that in the final VS 2005 bits, the TableAdapters will use timestamp fields for concurrency. I told him flatly I didn't think it worked, but I was wrong. If you create a Table in a Typed DataSet in VS 2005 and include the timestamp field in the select statement, it will use the timestamp field for concurrency. Awesome!
(Note: ASP.NET 2.0 DataSources use their own source code for concurrency so that doesn't work at all in DataSources AFAIK.)
In cooperation from Dunn Consulting and Training, we will be offering a new five-day course on Enterprise Data Architecture. The course will teach best practices from the ground up when it comes to implementing data solutions with Microsoft .Net tools and technologies.
I've blogged before about issues with the SqlDataSource. I've crufted up an example of the problems that can be downloaded here (with usual caveat of changing the connection string in the web.config to point to a DB with the Northwind database).
I have been a fan of Typed DataSets since the PDC Beta of .NET. I’ve been asked to detail my recent criticism of Table Adapters in the .NET 2.0 Typed DataSets. Here are the points that I am most concerned with:
Anything I missed?
Recently I posted about Timestamps and CommandBuilders and I got a well informed reply by Luciano Evaristo Guerche concerning a related approach of using BINARY_CHECKSUM in SQL Server to do the same thing. I think Luciano's response means to say that if you can't use Timestamp's in the database (like you don't have control over the schema) then BINARY_CHECKSUM is an improvement over the brute force concurrency that CommandBuilders do by default.
I've been digging into the latest version of the Entity Framework Beta (and designer CTP) that dropped a few days ago. I've concocted a small example that shows the derivation model in the Entity Framework. Essentially it is a small model that has a Product type and two types that derive from that: ActiveProduct and DiscontinuedProduct:
Over the past week there have been a flurry of new projects coming out of Microsoft, mostly in the form of CTP's. I've been downloading like crazy and will likely be discussing my experience with them in the coming week. In case you missed any of them:
I expect that with the release of the EF Beta 3 means Astoria is coming soon. I'll let you know when it drops! Time to start digging in.
Astoria has been renamed (ASP.NET Data Services) and added to the ASP.NET Extensions package (which includes the MVC support as well as other facilities). Looks like ASP.NET Data Services is slated for a release in Q2 2008. If you're interested in Astoria, go grab the CTP here:
Come see me and Glen Gordon talk at Phipps Plaza in Atlanta about Visual Studio 2008, "Astoria", Entity Framework and Silverlight...and see them working gracefully together!
I've been digging into the Entity Framework and Astoria and decided to create a quick little mashup of Silverlight and those two technologies. The result is this little product viewer using the Northwind database:
For those who do not know what the SilverlightData.com site is about...its an example of Silverlight 1.1 working with Entity Framework and Astoria. When I released SilverlightData.com last month, I had expected to allow users to download the source code so they can get a taste of what Silverlight 1.1 and Astoria together would look like. Unfortunately because of a bug on my part, the source link did not work. I've addressed that and you can now download the source code.
I've updated my Silverlight 1.1/Entity Framework/Astoria mashup to use the Astoria Silverlight Client API instead of raw JSON serialization. The code contains both methods (but they are switched out with a project-level #define). If you're interested in seeing how this works in practice, go grab the code. Here's a direct code link:
I've gotten the new Visual Studio Orcas March CTP up and running (as the VPC it ships as). I've been playing with the Entity Framework some today and I am pretty impressed so far. Unfortunately the automatic generation of the schema/mapping files still isn't working in this build, but if you write it out by hand it does work. I'll be posting an example soon.
I was reading an article about VB9's XML Literal support and why C# decided not to support it. (Note, I agree with C#'s lack of support for it, but that's not what this post is about). Paul Vick said:
The ADO.NET team has been working hard on a new release of the Entity Framework with a boatload of new features (I haven't played with it yet, probalby this weekend). I know they are under some pressure as the June CTP shipped on July 2nd. Check it out if you want to see where they are going.
On TheServerSide.NET, my new article introducing the concepts of the Entity Data Model (i.e. Entity Framework, ADO.NET v.Next, etc.). Let me know what you think!
|Implementing and Securing an API with ASP.NET Core (new)|
|Building a Web App with ASP.NET Core, MVC6, EF Core and AngularJS|
|Building a Web App with ASP.NET5, MVC6, EF7, and AngularJS (Retired)|
|Best Practices in ASP.NET: Entities, Validation, and View Models|
|Front-End Web Development Quick Start|
|Lessons from Real World .NET Code Reviews|
|Node.js for .NET Developers|
|Application Name||WilderBlog||Environment Name||Production|
|Application Ver||220.127.116.11||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.24628.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|