Jelle Druyts

"WSE 2.0 is now Microsoft.Web.Services2 and the config section is called <microsoft.web.services2>." [Via Early Adopter]

"WSE major versions are not simply incremental feature additions, they are different libraries. As such, they deserve different names." Sure, there are some good technical reasons to append the version number to the namespaces, dll's and config sections, but I don't like the smell of this. Stuff like "msxml.dll, msxml2.dll, msxml3.dll, msxml4.dll" springs to mind. Granted, those are libraries with incremental feature additions - they're not simply "different libraries" as is the case here.

It's sort of like calling your successor product "NT" (which in Windows-land stands for New Technology - or doesn't it?), "Next-Generation", or "The Revenge" for that matter.

I'm not calling this change dll hell, but it still feels icky. I wish that .NET would even have nice solutions for these kinds of "higher-level" versioning issues.