The number of built-in Activities that you can use to create a service that handles a long running service is small. Fortunately, it's easy to add additional Activities that wrap up business logic.
Making the right runtime design decisions can help -- or harm -- your program.
Peter Vogel helps you understand the benefits of dynamic loading at runtime.
Not all business operations finish in seconds. Using Windows Communication Foundation you can still create -- as a single project -- an application that supports business services that take hours (or days or weeks or months) to complete.
The WebGrid will certainly make the developers who use it more productive. But is it missing the point of the ASP.NET MVC model?
Since the best tool for creating a list is SharePoint itself, why not take advantage of it when deploying a new list to your SharePoint solution? Visual Studio 2010 lets you do that.
Faced with reviewing large swaths of other people's code, Peter Vogel is left to ask: what does it really take to be good at debugging?
Peter Vogel answers reader questions, including extending custom sections in the config file, using CreateQuery and ESQL in the Entity Framework, and reading lambda expressions.
Practical .NET columnist Peter Vogel ponders some of the assumptions and decisions that go into building out an SOA, and wonders if there might be better approaches.
Windows Communication Foundation has steadily evolved to better support SOA and Web services. Here's how to get the most out of your WCF-based services architecture.
If you're using the ASP.NET DataSources, you may be missing an important part of their functionality: the power of their events. But sometimes the right event isn't on the DataSource.
If you're considering a move into the world of LINQ and Entity Framework, you have to consider the possibility that LINQ and Entity Framework won't let you issue some bizarrely complicated SQL statement. Don't worry -- should that ever happen, you have options.
Faster performance in business applications comes down to reducing the "critical two" -- disk I/O and trips to the server. Doing that means doing a lot of things right, starting with your database design -- and tweaking your ADO.NET code helps, too.