Yes, you're right, Tony. Just let me know whom I need to beat up with you. :-p
Nice post, Tony.
There are also some easy ways to turn ViewState off by default too. I share some of these ways at the end of this post:
Controlling HTML in ASP.NET WebForms
First let me say good article and I really LOVE the new layout, and member community site good work!
I use viewstate alot for "other things" so I ended up just using sql for my session state and then throwing the viewstate into the session, then on my grids i just turn on full features hahahaha get super performance...
@Simone - Thanks. We actually have published the link on our asp.net community page. But again, I'm sure there are other companies out there who are emailing their customers telling them to "VOTE FOR US!" I think you're still capturing some great information, and the fact that you're an independent third party volunteering to manage this survey is the essence of the "developer community". However I still always caution reading too much into polls. You example is perfect - Infragistics is represented by a small 4% in your poll. Does that mean that a smaller number of developers are using Infragistics? Does it mean that the audience wasn't a random selection? Or does it mean that Infragistics customers are more likely to be working in a business environment where access to blogs and the internet is cut off? My point is that you must be cautious in the conclusions drawn from polls and surveys.
@Simone - Thanks for your input on use cases for each platform.
For the code analogy I made, I still meet developers to this day who will code in C++ because it gives them better performance and doesn't require the overhead of a garbage collector. I think the analogy is 100% relevant and shows the type of tradeoff that a developer needs to think about.
Tony, I see no need to jump on the MVC bandwagon when working with internal (intranet) web apps. If I was building a web app which faced the internet customer, I might be more inclined to go that route.
As a matter of fact, if I am truly trying to do something with an old windows application, I would be more inclined at this point to do a Silverlight app than a MVC.
Put me in the category of the folks who believe that the garbage collector doesn't do an adequate job of managing memory. I pay close attention to FxCop rule violations as it pertains to memory usage. Skip the ones on the names of my variables.
I cut my teeth on coding in C in 1985, and the kids today have no appreciation for the power that is memory. Ask someone today to conserve your variable space by using a bitwise mask, and note the blank stares. LOL. Heaven forbid I start talking about sparse files and seeking beyond the end of file such as what C on a UNIX box will let you do. I might as well as blasphemed.
@TheLudditeDeveloper - Yes, actually our Silverlight Line Of Business controls will be built directly on top of SL3. Even though SL2 was leaps and bounds ahead of SL1 in terms of building LOB applications, we felt that SL3 was much better suited compared to SL2.
@Kiran - That's great feedback, and obviously something that we want to keep an eye on ourselves. We're in no way limiting the number of features that go into the platform, it's actually quite the opposite. By removing 1 release cycle, the developers gain an extra month or more of development time. Time that would have been spent finailzing bits for the release. That regained time is spent building more features. They basically end up with an extra sprint of development time. Features that you would have waited 8 monts for in the past, are now getting to you 2 months sooner. That's the plan anyway, and it appears to be working well so far. But at the end of the day, we want what's best for you - the customer. So keep the feedback coming. BTW, you can always send feedback directly to the product management team via - productmanager at infragistics
While I understand why Microsoft is trying to be more agile, they are driving me a little crazy right now because of what I see as "compeating" technologies. Even within their own teams you will find conflict in guidance on what are the best tools to do the job. And so, I find it takes me a while to figure whose advice I "trust".
If you had asked me in May if Silverlight has a strong future, on a scale of 1-10, I would give it a 10. Now, I am not quite as sure, maybe an 8.5. Same for LINQ. I would now give it a 4 as I still continue to do a lot with classic ADO .Net. To me, the framework scenario requires a too simple of a database for it to have a strong fit. Too many of my data services perform aggregations, unions, etc to ever find myself in a scenario where I could bind in both directions.
I also would like the releases to be more in sync. For example, for SL 3 tools for VS 2008 SP1, Microsoft has basically "punted" in their ability to render SL XAML accurately in the designer. Thus relying on the user to use Blend 3.0. Problem with that is that at the current time, Blend is at RC mode, while Silverlight Tools is RTM. So, I have to wait for another add-on release. It's a good thing I don't plan to release this SL app until 2010.
From an IG perspective, I think that you guys are doing a good job with the release schedule. That being said, I think that things could have been communicated better on the SL LOB roadmap. For example, I never anticipated a switch from SL2 to SL3 midstream in your map. Maybe it was mentioned and I missed it. I also never anticipated the July test candidate release. We also "caught" the IG sample websites in a state of limbo in their state of being on SL2 or SL3. For example, visting the SL3 example page and being redirected to the SL2 samples. Or visiting the old SL2 samples and having it tell us we need SL3. I understand that kind of stuff happens, but I will use that as an example of how IG is being impacted by the whole agile scenario.
We don't always upgrade anyway. For example, we're still pushing out 2008.2 and we support 2007.2. Back in the 2005-2006 time frame when we upgrade frequently, we ran into a lot of IG bugs which required hot fixes every time there was a new IG release. Nowadays, I can't recall the last time that I have opened a support ticket, but then again you knowledgable guys have been a bit more accessible (thank you).
Lots of Luck on all of your future endeavors!!
All the best, Tony! You'll be missed!
You may have come across articles about the end of support for ASP.NET WebForms and how you should consider