3 ms·

I actually think there is a lot here to get excited about. .net forms getting model bindings is quite big, as taken from MVC. Page speed performances, html5 sup

I actually think there is a lot here to get excited about. .net forms getting model bindings is quite big, as taken from MVC. Page speed performances, html5 support, web socket support. It seems to me they are actually taking their head out the sand and realising the web is not all about Microsoft now and there is a whole world of new technology happening around them that they need to include in their products. I have actively pulled my Silverlight projects now and am concentrating on html5, javascript and websockets since last night. Massive coincidence that this morning Silverlight is getting a bum deal in other press. I think this is a prelim release to 5 as they want to show their commitment to becoming more engaging to html5 standards and other technology. Also, there is a comment that this is a weak release for 2.5 years work, .net 4 had a massive amount of work done on it and this is a partial release. The library is already very concise so I would be interested to know what "massive" changes they could make right now apart from just making the library more stable. Consider this the Windows version (in development terms) of the Leopard to Snow Leopard that Apple released.

mattmanser 15y ago
All the html5 stuff is in there because of windows 8, pure and simple. Also I don't know who in their right mind would chose to use classic ASP.Net anymore. But compared to 3.5 there's nothing in here that I find exciting or that's looking particularly like it's going to make my life as a programmer better. Personally I find the more they work on MVC the more they seem to be giving in to the temptation to put 'magic' in there like the old forms, which sucks imo as it encourages new programmers to write very bad code.
- chrislomax 15y ago
  We actively use asp.net "classic" as you have referred to it. It's an alternative and in by no means inferior to MVC. We are looking at implementing MVC3 but to do what we do with asp.net webforms will be a difficult task. We wrote a CMS framework for our own clients and we use quite a lot of specific .net webforms controls to do what we do. The main reason I started moving away from silverlight and more into html and js, mvc etc was because of Windows 8 not having silverlight as part of the interface. This is exactly what I mean by Microsoft getting it's head out the sand though, they have chosen to use the more adopted methods going forward than it's own solutions. It's a sign that Microsoft are no longer at the center of the universe. I'm not putting down your comment on who in their right mind uses "classic" asp.net any more but I find it a little closed minded as asp.net webforms is far more tried and tested. It's a developers choice and it's not a wrong choice to use forms over mvc.

mattmanser 15y ago

All the html5 stuff is in there because of windows 8, pure and simple. Also I don't know who in their right mind would chose to use classic ASP.Net anymore. But compared to 3.5 there's nothing in here that I find exciting or that's looking particularly like it's going to make my life as a programmer better. Personally I find the more they work on MVC the more they seem to be giving in to the temptation to put 'magic' in there like the old forms, which sucks imo as it encourages new programmers to write very bad code.

chrislomax 15y ago
We actively use asp.net "classic" as you have referred to it. It's an alternative and in by no means inferior to MVC. We are looking at implementing MVC3 but to do what we do with asp.net webforms will be a difficult task. We wrote a CMS framework for our own clients and we use quite a lot of specific .net webforms controls to do what we do. The main reason I started moving away from silverlight and more into html and js, mvc etc was because of Windows 8 not having silverlight as part of the interface. This is exactly what I mean by Microsoft getting it's head out the sand though, they have chosen to use the more adopted methods going forward than it's own solutions. It's a sign that Microsoft are no longer at the center of the universe. I'm not putting down your comment on who in their right mind uses "classic" asp.net any more but I find it a little closed minded as asp.net webforms is far more tried and tested. It's a developers choice and it's not a wrong choice to use forms over mvc.