For my first trick, I was reading about this and may want to refer to it later. Not high-tech, not fancy, nothing about the deep internals of .NET.

PageMethods enables reliable URLs.
Linking to a web page is very easy, both in simple HTML and in ASP.NET.
Linking to a page that really exists, passing the right parameters, and parsing these parameters, is a bit different.
PageMethods takes care of your URLs. It proposes a solution to define structured URLs for each of your pages, as well as a clean and simple way to call them.

This seems like a useful method for dealing with this issue. I just don't know how much this issue comes up.

http://blogs.msdn.com/powertoys/archive/2005/12/07/PageMethods.aspx

One of the consultants at our current client was talking last week about a bug in the ASP.NET 2.0 runtime when they handle async pages. I haven't played with those yet, so wasn't sure how they work, or that they exist at all.

(The bug he was describing was that as the runtime decides to spawn a thread to process [the remainder of] a page, they copy all the thread principal, etc. However, they apparently do NOT copy the thread local storage data - usually stored in the .NET CallContext)

Anyway - here's a quick blog post about how an ASP.NET 2.0 async page can work with async a WCF service.

Wenlong Dong's Blog : ASP.NET Async Pages vs Async WCF Service Operation

I saw this MSDN mag article by Aaron Skonnard a while ago, and am now revisiting it to understand the differences between WCF, ASMX 2.0 and WSE 3.0, especially as they relate to SOAP protocols and compatibility with older non WCF-aware clients (think VB6, ugh)

There are some good Q&As in here, along with a table (figure 4) that describes the diffs.

Service Station: All About ASMX 2.0, WSE 3.0, and WCF -- MSDN Magazine, January 2006

We've been doing some heavy WCF debugging lately at my current client. The E2E trace files get big and very hard to read.

You can use svcTraceViewer.exe to make viewing the data much more fun. Along with this, here's some more info about emitting call stacks in the trace output.

kennyw.com » Blog Archive » Enabling E2E Tracing for WCF

Now free to develop, deploy, and distribute. Not that I would opt for this over SQL Express, but since my current client is using Oracle, this is good to know...

Oracle 10g XE (express edition) download here

Well, nDoc has fallen behind the times, not really supporting all of .NET 2.0 yet. Namely, generics are not supported in the latest released version of nDoc.

Here are some tricks to work around it:

nDoc Wiki has some info about .NET 2.0 support, but the Wiki is down for now.
Using Google caching, I grabbed the page by searching for ".net 2.0" ndoc support then looking at the cache page.

The above wiki/cache page talks about a config file change to support 2.0. But then it goes on to link to some dude's blog where he's got a 2.0 compatible version working.

nDoc 1.3.1 v16