title: .NET 3.5 published in 11/07 .NET 3.0 in 11/06. Why are most people still using .NET 2.0?
body: <p>People have been developing own solutions to the following problems:</p>
  
  <ul>
  <li>Consistent messaging frameworks for remote information exchange (webservices,rpc,...) </li>
  <li>SDK's for state managements for things such as Finite State Machines and Workflows</li>
  <li>Authentication Frameworks </li>
  <li>And much more.</li>
  </ul>
  
  <p>For over <strong>two years</strong> now, Microsoft offers .NET 3.0 which contains consistent and well documented so called Foundations for Workflows, Communication, Authentication and a new way to build web apps.</p>
  
  <p>However,... people were still building own frameworks with consistent object relational mapping to address their databases, own techniques to dynamically extend classes and methods at runtime (for customer to be able to customize application behaviour e.g.).</p>
  
  <p>For <strong>over one year</strong> now, Microsoft offers .NET 3.5 which - amongst others - contain LINQ and therefor a great ORM and wonderful means to extend your code and make it much easier to write code after all.</p>
  
  <p>But look around... it seems as if the majority still uses .NET 2.0. Websites are created in plain ASP.NET. Desktop experience is still achieved with a combination of CSS, JavaScript and HTML. Executables are using plain old WinForms, workflows are implemented with delegates, events, do/while and switch/case.</p>
  
  <p>Without too much discussion, I would be glad to see concrete reasons for the following question:</p>
  
  <p>In your opinion: Why is it that people don't jump onto the .NET 3.5 train?</p>