Archives

Archives / 2010 / November
  • ASP.NET Ajax will not be left behind the HTML5 rush

    It takes a short overview of Microsoft development tools and platforms evolvement in order to demonstrate the importance of supporting Web Forms development for ASP.NET Ajax with HTML5 enhancements. In an article that Todd Anglin publishes in Redmond Developers, under the title "Silverlight: What Web Forms Wanted to Be", Todd says that ASP.NET was supposed to be Web Forms. A framework that meant to duplicate VB6 ease of development or rather its more mature successor Window Forms. Asp.Net was expected to deliver this simple and easy development paradigm for web. But it failed, Microsoft could not reproduce stateful based development paradigm for a stateless environment. Years later Microsoft rolled out Silverlight that is really another trial to come up with Web Forms paradigm for website development. Todd says in his article " Silverlight is what Web Forms wanted to be, a stateful application development model that can be deployed and updated as easily as traditional Web sites. Unencumbered by the limits of stateless pages, developing for Silverlight finally achieves what ViewState could not: It allows traditional desktop application developers to reuse their skills and development patterns for applications that can be deployed with no installation, save for the Silverlight plug-in"

  • New tool helps modernizing Client/Server apps to VWG ASP.NET

    Upgrading a Client/Server desktop based application to ASP.NET Web or Cloud based environment is thought to be a very complex and risky process. Most of us are intimidated only by the thought of taking one of our large, business applications; one that we have been working on for quite a while now, not to say mission critical and migratie it to a differernt technology. Most of us will follow the good old saying: If it ain't broken why fix it, right?! Which means that we will eventually find our selves with a very large and old system which the only possible solution for modernizing it would be the costly rewrite that we probably cannot afford or don't have the tme to wait for.