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).
Until The ServerSide .NET can post the sample code, I am posting it here
My newest DevSource article is live. It is about how to write Windows Live Messenger Addins with .NET. Check it out
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.
I am one of the authors of the upcoming Microsoft MCST Training Kit (Exam 70-536) book from Microsoft Press. If you are planning to take the test, this book should help you get ready for it:
I've been scratching my head at the ASP.NET 2.0 TreeView control. This control is meant to show a tree of items and each item can have a link to it. For example, this is what I use for my menu on the left of the page.
While I think its interesting that the new drop of WinFS will be shown at the upcoming TechEd (too bad I couldn't get there this year), what I have seen so far doesn't have me too excited. I played with Beta 1 a bit and was certainly a FanBoy for the early WinFS with Vista before that got yanked.
Thanks to Shawn Van Ness, he pointed me at this great utility that is helping me clean up some bad MSI's that are not letting me get WinFX installed correctly. Check it out.
Avalon WPF DataBinding Article has gone live on MSDN. Take a look. Part 2 will be published next week.
Every week (until I run out of Gems), I will post a new class or structure that I find in the .NET Framework that I never knew existed...and that I think rocks...
I was talking with a bright guy inside the ADO.NET team today when he told me that the DbCommandBuilder supports a new option called ConflictOption. This option alerts the DbCommandBuilder to use one of three methods for detecting concurrency conflicts:
I read a lot of technical books. There are few to which I can say I enjoyed reading. Jeffrey Richter's new opus is one of them. Even at 600+ pages, it is an easy read with a ton of very important information. Chapters 23 & 24 alone are worth the price of the book (no one gets threading issues like Jeffrey Richter).
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.)
I've gotten a couple of questions about a quick little Windows Messenger Add-In I wrote after watching the Channel 9 Video about how IM works. You can get the information on how to write your own add-in for Windows Messenger at Katie Blanch's Blog:
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.
Big thanks to Scott Guthrie in championing the Web Application for ASP.NET 2.0! I love using the old ASP.NET model (instead of the ackward Web Site project). I have now completely converted to the new format and I am very happy with the way it worked in almost every way.
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).
In case you didn't see it on other sites, it looks like MS has reversed its decision to wait until 2007 for the SP1 of Visual Studio 2005. Its coming by September.
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.
On Fritz Onion's blog, he mentions that the manuscript for Essential ASP.NET 2.0 should be done by Monday. I am itching to get a copy of that book when it comes out.
I have been attempting to try out some new software from Microsoft (including Glidepath and Visual Studio Database Edition). Both of these require SQL Server Express installed. Problem is that I install a Developer Edition of SQL Server 2005 (as well as 2000) because it is more feature friendly than SQL Server Express. Why does Microsoft insist I have a third Database server? Why can't it prompt me to tell it what database to use, or at least attempt to find SQL Server 2005 as the default instance on the current machine? Just stoopid in my opinion. It's keeping me from trying out and possibly exhaulting these new interesting projects.
"There I said it..."
|Using Visual Studio Code for ASP.NET Core Projects (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||18.104.22.168||Runtime Framework||.NETCoreApp,Version=v1.1|
|App Path||D:\home\site\wwwroot||Runtime Version||.NET Core 4.6.25211.01|
|Operating System||Microsoft Windows 6.2.9200||Runtime Arch||X86|