.Net patterns vs. GOF
.net, design-patterns
Solution
The idea with the GoF book wasn't to be language-specific, although they did provide samples to better explain the designs.
The idea was to provide patterns which appear again and again in software design, and something of a cookbook that any developer can use to implement those patterns as needed in their language of choice.
That said, when you look at .NET, as others have mentioned, you will see several of the design patterns implemented as first-class citizens right in the framework.
Are there any "not of use" because of a language? No. The patterns will continue to be useful, even if some are already implemented for you.
Problem
Since the GOF book was put together well before .Net came into being, are there any specific patterns described in GOF that are not appropriate for .Net? And if so, for what reason? This is a question relating to a recent bounty discussion.