Practical .NET


Understanding .NET Using Read-Only Collections

Even if you're not working in the Microsoft .NET Framework 4.5, .NET provides you with a way to create a read-only collection or to convert an existing List into a read-only collection.

Unity vs. MEF: Picking the Right Dependency Injection Manager

Peter Vogel compares both of the Microsoft dependency injection managers/inversion of control containers and comes up with a decision tree for picking the correct one.

Shorten Your Backlog: Integrating ASP.NET and SharePoint

Integrating your .NET line-of-business applications with SharePoint is easy to do and allows you to transfer a ton of work from your desk to your users' desks.

Redefining Mobile UIs with ASP.NET

Because the mobile platform has come later in the history of computing, developers have gotten in the habit of redesigning desktop applications for the handheld device. Peter Vogel thinks developers have that backward, and that the UI design process shows the way out.

Configuring WCF Routing Without Code

Peter Vogel returns to creating a Windows Communication Foundation (WCF) router that loosely couple services with their clients. But this time he uses XML to configure his router rather than doing it in code.

Strategy, State and Role Patterns in .NET

Implementing design patterns in the Microsoft .NET Framework isn't all that hard to do; understanding what each pattern does for you and picking which one to use is the real issue.

Windows Workflow and Timeouts

Workflows make it easy to do something that's very hard to do in any other development environment: Take action when something doesn't happen. Here's how to protect yourself when something's isn't happening in your Windows Workflows.

The User Interface Design Process

There's a well understood UI design process that you can use to get to the "right" UI for your application. And it starts by inventing people.

Integrating SharePoint Web Parts: Providers, Filters and More

Creating connectable Web Parts is a good thing for you and your users -- and the default interfaces that come with SharePoint form the architecture you should use to create those Web Parts.

Implementing the Default SharePoint Interfaces with Lists

Peter returns to creating a provider WebPart, but this time passes SharePoint list data from one WebPart to another.

Passing Selected Data Between WebParts in SharePoint

The IWebPartParameters interface provides a flexible way for one WebPart to select the data it wants from another WebPart. And, since implementing that interface doesn't require much code, you should consider using it on all your WebParts.

SharePoint Web Part Default Interfaces

Because SharePoint lists are automatically turned into connectable Web Parts, you can integrate your own Web Parts with any existing SharePoint list by implementing the default interfaces provided by SharePoint.

Faking the Rest: Detouring Properties, Shimming Parameters and More

Peter finishes up his discussion of using the Fakes Framework with TDD in Visual Studio 2012 Ultimate by looking at mocking properties and why you'd want to pass a shim as parameters.

Faking it Well: Effective Mocking with the Fakes Framework

Using shims in Visual Studio 2012 Ultimate lets you easily bypass code—no matter how deeply buried—to test just the parts of your application that you want to test.

Build an ASP.NET JavaScript Generator

ASP.NET provides a wealth of options for dynamically integrating JavaScript into your client-side pages. And by adding T4 into the mix, you can generate, at runtime, exactly the client-side code that your page needs.

Upcoming Events

.NET Insight

Sign up for our newsletter.

I agree to this site's Privacy Policy.