Comments on: 10 Features why Asp.Net 4 is better for public website http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/ podcast addict, believes in occam razor, software consultant Thu, 11 Mar 2010 21:18:41 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Fajar http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-404 Fajar Tue, 20 Oct 2009 12:17:40 +0000 http://www.ronaldwidha.net/?p=326#comment-404 Yes of course. My work is not going live until June 2010, so if .net4<br>could really make it to final version in Q1 of 2010, I think I can<br>spend a few weeks just messing around. Or maybe work on it for the<br>next iteration. Who knows. Yes of course. My work is not going live until June 2010, so if .net4
could really make it to final version in Q1 of 2010, I think I can
spend a few weeks just messing around. Or maybe work on it for the
next iteration. Who knows.

]]> By: ronaldwidha http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-403 ronaldwidha Tue, 20 Oct 2009 12:10:49 +0000 http://www.ronaldwidha.net/?p=326#comment-403 Having control over ID is indeed pretty sweet. However, you can still disable viewstate on <a href="http://asp.net" rel="nofollow">asp.net</a> 3.5, just not site-wide I don't think.<br><br>Remember you'll be working on beta technology (<a href="http://asp.net" rel="nofollow">asp.net</a>, .net4 and vs2010 are all still in beta). Watchout for <a href="http://Asp.net" rel="nofollow">Asp.net</a> 4 beta 2 is out 19th October for MSDN subscriber and general public on 21st. Having control over ID is indeed pretty sweet. However, you can still disable viewstate on asp.net 3.5, just not site-wide I don't think.

Remember you'll be working on beta technology (asp.net, .net4 and vs2010 are all still in beta). Watchout for Asp.net 4 beta 2 is out 19th October for MSDN subscriber and general public on 21st.

]]> By: Fajar http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-402 Fajar Tue, 20 Oct 2009 12:03:11 +0000 http://www.ronaldwidha.net/?p=326#comment-402 Nice! I might consider porting my current work to ASP.NET 4 just for point number 5 and 6. Nice! I might consider porting my current work to ASP.NET 4 just for point number 5 and 6.

]]> By: ronaldwidha http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-401 ronaldwidha Tue, 20 Oct 2009 11:47:03 +0000 http://www.ronaldwidha.net/?p=326#comment-401 Looking at the <a href="http://Asp.net" rel="nofollow">Asp.net</a> 4 overview document, there isn't seem a whole lot of information about what gets deprecated. But my guess would be it's gonna be straightforward. From <a href="http://ASP.net" rel="nofollow">ASP.net</a> perspective, all the web controls and http related classes are still supported.<br><br>So is in terms of the language support and overall .Net framework stuff. I'd be surprised if it was as troublesome as .Net 1.1 to .Net 2.0. Back then there was a shift how the web project was handled, etc. It's not the case from 3.5 to 4 Looking at the Asp.net 4 overview document, there isn't seem a whole lot of information about what gets deprecated. But my guess would be it's gonna be straightforward. From ASP.net perspective, all the web controls and http related classes are still supported.

So is in terms of the language support and overall .Net framework stuff. I'd be surprised if it was as troublesome as .Net 1.1 to .Net 2.0. Back then there was a shift how the web project was handled, etc. It's not the case from 3.5 to 4

]]> By: Fajar http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-400 Fajar Tue, 20 Oct 2009 11:39:16 +0000 http://www.ronaldwidha.net/?p=326#comment-400 Good news there! Any ideas about porting existing ASP.NET 3.5 to this version? Good news there! Any ideas about porting existing ASP.NET 3.5 to this version?

]]> By: Fajar http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-384 Fajar Tue, 20 Oct 2009 05:17:40 +0000 http://www.ronaldwidha.net/?p=326#comment-384 Yes of course. My work is not going live until June 2010, so if .net4<br>could really make it to final version in Q1 of 2010, I think I can<br>spend a few weeks just messing around. Or maybe work on it for the<br>next iteration. Who knows. Yes of course. My work is not going live until June 2010, so if .net4
could really make it to final version in Q1 of 2010, I think I can
spend a few weeks just messing around. Or maybe work on it for the
next iteration. Who knows.

]]> By: ronaldwidha http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-383 ronaldwidha Tue, 20 Oct 2009 05:10:49 +0000 http://www.ronaldwidha.net/?p=326#comment-383 Having control over ID is indeed pretty sweet. However, you can still disable viewstate on <a href="http://asp.net" rel="nofollow">asp.net</a> 3.5, just not site-wide I don't think.<br><br>Remember you'll be working on beta technology (<a href="http://asp.net" rel="nofollow">asp.net</a>, .net4 and vs2010 are all still in beta). Watchout for <a href="http://Asp.net" rel="nofollow">Asp.net</a> 4 beta 2 is out 19th October for MSDN subscriber and general public on 21st. Having control over ID is indeed pretty sweet. However, you can still disable viewstate on asp.net 3.5, just not site-wide I don't think.

Remember you'll be working on beta technology (asp.net, .net4 and vs2010 are all still in beta). Watchout for Asp.net 4 beta 2 is out 19th October for MSDN subscriber and general public on 21st.

]]> By: Fajar http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-382 Fajar Tue, 20 Oct 2009 05:03:11 +0000 http://www.ronaldwidha.net/?p=326#comment-382 Nice! I might consider porting my current work to ASP.NET 4 just for point number 5 and 6. Nice! I might consider porting my current work to ASP.NET 4 just for point number 5 and 6.

]]> By: ronaldwidha http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-379 ronaldwidha Tue, 20 Oct 2009 04:47:03 +0000 http://www.ronaldwidha.net/?p=326#comment-379 Looking at the <a href="http://Asp.net" rel="nofollow">Asp.net</a> 4 overview document, there isn't seem a whole lot of information about what gets deprecated. But my guess would be it's gonna be straightforward. From <a href="http://ASP.net" rel="nofollow">ASP.net</a> perspective, all the web controls and http related classes are still supported.<br><br>So is in terms of the language support and overall .Net framework stuff. I'd be surprised if it was as troublesome as .Net 1.1 to .Net 2.0. Back then there was a shift how the web project was handled, etc. It's not the case from 3.5 to 4 Looking at the Asp.net 4 overview document, there isn't seem a whole lot of information about what gets deprecated. But my guess would be it's gonna be straightforward. From ASP.net perspective, all the web controls and http related classes are still supported.

So is in terms of the language support and overall .Net framework stuff. I'd be surprised if it was as troublesome as .Net 1.1 to .Net 2.0. Back then there was a shift how the web project was handled, etc. It's not the case from 3.5 to 4

]]> By: Fajar http://www.ronaldwidha.net/2009/10/18/10-features-why-asp-net-4-is-better-for-public-website/comment-page-1/#comment-378 Fajar Tue, 20 Oct 2009 04:39:16 +0000 http://www.ronaldwidha.net/?p=326#comment-378 Good news there! Any ideas about porting existing ASP.NET 3.5 to this version? Good news there! Any ideas about porting existing ASP.NET 3.5 to this version?

]]>