Web Forms

ASP.NET MVC vs. Traditional ASP.NET {4}

by Brent K
These days, on average, one in every four websites you come across on your daily browse will be written in ASP.NET, but on the newer and presumably better ASP.NET MVC framework, you may find a meager 1 in 100. So what’s the difference?  What distinguishes one over the other?  Is one a newer version of the other?  I aim to answer all these questions and more in this small commentary. read more...

ASP.net Code Cloning {1}

by Robert L
Frequently change in requirements, tight delivery deadline and complex application architecture slow down web applications development and encourage code cloning. Web application frameworks mainly support developers to speed up development by providing libraries for database access, session management, and they often promote code reuse. In this paper, we provide a systematic study of cloning in six (6) Web Applications of different sizes, developed using Classic ASP.NET and ASP.NET MVC framework to find out whether there is any relation between frameworks and code cloning. The contribution of our study is: 1) the study results shows which framework in .NET technology can be chosen to avoid cloning in development of web application; 2) the cloning metrics that we have calculated and applied in our study may be useful in other similar studies. read more...

ASP.NET Web Forms versus MVC Framework {Comments Off on ASP.NET Web Forms versus MVC Framework}

by Han C

Web developers have a choice between using ASP.NET Web Forms or ASP.NET Model-View-Controller. ASP.NET Web Forms is an older but faithful option for developers to work with in creating websites. The Model-View-Controller is essentially a newer way for developers to structure their design patterns by dividing an application up into more concise areas of focus. The article talks about the popularity and adoption of the MVC framework in IT organizations and the impact on Microsoft’s ASP.NET development platform. As usual, companies must take into consideration the costs associated with startup costs but benefits for developers start with the power of flexibility. For example, flexibility to enable development “of pure Ajax solutions without typing .a. site to a specific commercial framework. What this means is that instead of having to deal with a “thick abstraction layer built on top of Web Forms (view state, server controls, page controllers, event based page life cycle)”, MVC permits developers to build more interactive and responsive applications with components they are comfortable with such as Ajax. Furthermore, it allows programmers to have more control over the code they write. read more...