Microsoft have released significant parts of the .NET framework source code for developers using Visual Studio 2008. In case you've not been following the releases, this blog post includes links to configuration and hotfix resources.

By default, WCF limits the amount of data that can be transferred through an operation invokation in subtle ways. To override these default limits, you will need to alter both the client and service configuration. No changes to your code are needed, though.

I've recently begun playing around with developing an SOA solution using WCF. My focus is on implementing a service that is loosely coupled, autonomous, highly configurable and reusable. I might tell you more about it in a later blog, but for now I want to describe some of the design issues involved.

Recently, I began having problems with Virtual Server 2005 R2 on my Windows XP computer. I was not aware of anything having changed, except suddenly my VPCs couldn't find a network adapter. Facing the possibility of a complete laptop rebuild, I was scouring the net for a solution...

I've been playing around a bit with the idea of integrating Windows Workflow Foundation into custom web server controls. I've had some success but also hit something of a wall. If you have any experience with any of these issues, I'd love to hear from you.

I've recently hit an issue where some custom controls have been generating exceptions when unpublished pages exist in an EPiServer site. In these cases, the relevant (required) properties have null values.