DXperience v2011 vol 2 will require .NET 3.5 or later

ctodx
22 November 2011

Way back in June, we had a mini-summit with the various team leads discussing the just-released DXperience v2011 vol 1 and whether we wanted to change anything for v2011 vol 2. One of the resounding requests was to move our WinForms and ASP.NET webforms controls to require .NET 3.5 or later. I wrote a blog post immediately afterwards with this news, and the vast proportion of comments on that post supported the move.

Modifying old typewriter for 21st century(Aside: our WPF and Silverlight products already require Visual Studio 2010 and .NET 4.0 so that we can provide the best design-time and run-time functionality. Of course ASP.NET MVC requires Visual Studio 2008 or later and .NET 3.5 or later anyway.)

Now that we’re close to releasing v2011 vol 2, I thought it would be a good idea to remind our WinForms and WebForms customers that this release will only support Visual Studio 2008 or 2010 and only target .NET 3.5 or above. If you are still using Visual Studio 2005 or .NET 2 for those kinds of apps, you should start to make plans to migrate to a later IDE and run-time.

Note that we will continue to publish minor bug-fix releases to the v2011 vol 1 line, just as we did when v2006.3 became the final version to support the original Visual Studio .NET and Visual Studio 2003 (and .NET 1.x). The new features and enhancements for 2011.2 have been written using .NET 3.5 and so they can’t be back-ported to 2011.1.

And no, before you ask, I can’t tell you when we’ll be releasing 2011.2, just that it’s “close”. Everybody here is working extra hard to give you the best release of DXperience we’ve ever provided. Stay tuned!

11 comment(s)
Neal
Neal

I'm happy to hear this, however, as the comments to the prior blog article overwhelmingly requested, make the move to .NET 4 as the minimum.  I hope the core of this and future builds will take advantage of parallel, threading, and the good practices of the present day we should be focusing on.  I'm interested to hear why you chose .NET 3.5 instead of 4?  It's free, so why not?  It's just like building iOS apps, why support legacy versions when iOS updates are free?  We have to not be afraid to cut ties with the past.

22 November, 2011
Ruchit Surati
Ruchit Surati

"Everybody here is working extra hard to give you the best release of DXperience we’ve ever provided. Stay tuned!"

This is the most awaited DevEx release so far. Why do I feel you're up to releasing the new 'iPhone thing' in developer tools segment...

22 November, 2011
Travis Illig
Travis Illig

Does this also include DXCore so plugins can assume .NET 3.5 and above?

22 November, 2011
Julian Bucknall (DevExpress)
Julian Bucknall (DevExpress)

Neal: Maybe next time ;)

Ruchit: We're glad you're on the edge of your seat. Wait 'til you see what we've got!

Travis: Absolutely. DXCore will assume .NET 3.5 or above.

Cheers, Julian

22 November, 2011
Crono
Crono

@Neal: .NET 4 might be free, but Visual Studio 2010 isn't... :)

22 November, 2011
renejdm
renejdm

If you can use Visual Studio 2008 with .NET4 then I am all for it. Since I have no intention of moving to Visual Studio 2010, I am glad that I can continue to subscribe to Devepress components for another year (or so).

22 November, 2011
abdulkadir cakir
abdulkadir cakir

Super

Im using Visual Studio 2010

22 November, 2011
Peter Thorpe
Peter Thorpe

@Neal If you are only using DevExpress components and your own code that is fine but if you you have dependencies on other 3rd party products it can be a major problem. We were unable to move to .NET 4 until a few months ago because a third party library didn't support it.

22 November, 2011
Hassan Gular M.
Hassan Gular M.

This is great news. From what you have seen so far, are their substantial performance gains along with the understood devx-dev's relief through .NET 3.5 features? In percentage, how much of WinForms and ASP.NET suites are now converted to .NET v3.5? This blog post came in pretty late since the first sighting of DXperience v2011 Vol. 2... you didn't changed the Target Framework Property and recompiled, did you now? LOL.

Seriously, I'm pretty crazy about this. It could have been .NET v4.0 but .NET v4.0 is already on the brink of being ousted by .NET v4.5... So .NET v3.5 was definitely the next logical step and here in Pakistan, 90% software houses are still suing Visual Studio 2008.

Great Stuff.

23 November, 2011
Daniel Motos Guerra
Daniel Motos Guerra

Finally a blog post. I was worried. I hope that from now on, these causeways are most abundant.

23 November, 2011
Scott G Blood
Scott G Blood

Am also glad this release and hopefully the next major release still have support for .net 3.5.

Working in a huge corporate environment where upgrading any components in windows is no simple task, if devexpress were to only target .net 4.0 within the next year at a minimum i can see my subscription renewal being refused when submitted to management as i would not be able to show any clear benefits of renewal other than bug fixes and considering we are usually a couple of minor version behind anyway, this isnt normally an issue as nothing is released until it is trounced on to within an inch of its life.

Cheers.

24 November, 2011

Please login or register to post comments.