I have been listening my way through the back catalog of Dot Net Rocks.
There have been some reoccouring questions:

How do I move a web service
How do I keep my code updated with respect to changes in my database structure.

There stock answers are:

You should never need to move a web service.
You should design your database up-front so it should not need to change.

These are grossly simplified. I have encountered a case where a website had to move due to legal questions about the name – the site had been located where it was for a year. Web services can and will suffer the same fate.

Database structures will change. We had to add an entire subsystem to the product that we are working on to support one line in the requirements. Change happens. The trick is to use tools that minimise that change. That can mean restricting the use of strongly typed datasets.

Guys please think about your snappy answers.

I have been investigating .NET Remoting from a VS Client.
The IDE will only allow references to dll’s while the command line will allow references to exe’s.

Since the command-line tools do allow this this seems to be a pointless restriction.

Look at this once the slasdhot effect has subsided.

Greasemonkey is a site customization utility.
You alter the browser’s behaviour for the specific site.
This allows massive customization.

Have a quick look at this.

What the hell are microsoft thinking of?
Intellectual Property is the vague cover for the merging of the distinct areas of

• Copyright
• Patent
• Trade Secrets

Intellectual Property Theft is a meaningless concept. The actual crime would be a Copyright/Patent/Non-Disclosure agreement violation which is not theft.

This company: elegancetech has a utility called C Sharpener for Visual Basic.
$99 dollars for a single user licence looks to be very good value.

This would be great for C# shops that have to take over maintenence of VB.NET code.

While it is great that .NET allows cross language work life is much easier if a shop sticks to one language. It would be a different matter if the two langauges were different in their expressiveness (say a functional language versus an OO one) but having two similar languages adds nothing to the mix.

I have nothing against VB.NET itself (Visual Fred), as it has finally gained the language features (inheritance, sane error handling) that Delphi has had since version 1 (10 years ago). The problem is the 3 million claimed VB (VBA) programmers. While the top few percent of those are likely to be decent devlopers the vast majority have the programming experience of  record macro then (possibly) edit. This leads to unmaintainable code. I have worked alongside professional VB developers whose idea of code reuse within a project consisted of cut-and-paste at best and the creation of reusable routines was a novelty.

Open source XAML implementation

An even smaller XAML implementation

Here are some really useful utilties.

They include decompilers, resource editors and games.

Async Delegate Article in C#

MyGenerator this is another free code generator