Talk:ASP.NET

Session State sharing nowhere to be found
This part seems incorrect: On IIS 6.0 and lower, pages written using different versions of the ASP framework cannot share Session State without the use of third-party libraries. This criticism does not apply to ASP.NET and ASP applications running side by side on IIS 7. With IIS 7, modules may be run in an integrated pipeline that allows modules written in any language to be executed for any request.[18] It seems there is no (easy) way to share session state between ASP.NET and legacy (or classic) ASP pages both placed in the same directory (hence in a same web application). There a lot of solutions involving databases and a lot of changes on both places (ASP.NET and ASP), but nothing working out-of-the-box. Is it possible this statement to be valid only for ASP.NET applications, say one that is 1.1 and another that is 2.0? --85.130.3.78 (talk) 11:23, 23 March 2009 (UTC)

Clean code
The article refers to "clean code" without a link. Quotation marks are around "clean", but not "code". If this is a reference to Robert C Martin's concept of clean code, I recommend extending the quotation marks to surround both words, and making that a link, either to an article on clean code, or at least to the one on Martin. Unfree (talk) 16:01, 4 November 2009 (UTC)

Information about ViewState incorrect
The viewstate does not track form values, it's a source of confusion amongs a lot of ASP.NET programmers.

Form values are already sent with the postback data, so these don't have to be in the viewstate. See:
 * http://msdn.microsoft.com/en-us/library/ms972976.aspx
 * http://weblogs.asp.net/infinitiesloop/archive/2006/08/03/Truly-Understanding-Viewstate.aspx

Viewstate only has to contain the state which changed from the defaults set in the ASCX files and OnInit method. That includes:
 * modifications by a event handler (e.g. showing an panel after a OnClick event -> the Visibility has to be tracked and restored)
 * modifications by the `Page_Load` event.

Programmers who fill the default Page_Load method, end up with a huge ViewState. This state is transmitted back and forth with every page request, causing performance issues.

Vdboor (talk) 09:42, 10 December 2009 (UTC)

WHY WE USE ASP.NET,WHY NOT USE PHP OR JAVA# —Preceding unsigned comment added by 220.226.191.107 (talk) 03:51, 9 January 2010 (UTC)

Faulty Criticisms
I believe the criticism section parts regarding session/state management was written by someone who did not fully understand the technology. What is being refered to here are inprocess sessions, one of the many ways ASP.NET/IIS can handle session data, and only a valid solution for the smallest of deployments. Session data storage is typically handled outside of the webserver that way a single site can be serviced by many web servers and gracefully handle server failures.

ASP.NET handles using sql as a session store, and comes with scripts to build these databases (except .net 1.0 which is located here. http://support.microsoft.com/kb/311209 )

There are plenty of valid criticisms to make about ASP.NET (Memory use, first hit compiling delay, inability to really just use the pieces you want, not embracing friendly/suffixless urls, etc) without traveling down such subjective criticisms  —Preceding unsigned comment added by 97.102.228.141 (talk) 06:29, 25 February 2010 (UTC)


 * Just come across this page and the criticism is mostly unsourced. I'm going to remove the unsourced material as original conclusions which don't appear to be coming from a third party source. Like you say, there is criticism out there which is citable, however the current criticism does not seem appropriate without sources. --Bill (talk 10:31, 16 May 2010 (UTC)

"At the server side, the application may change the viewstate, if the processing requires a change of state of any control." Huh? This isn't a well formed sentence... —Preceding unsigned comment added by 99.224.141.81 (talk) 17:29, 10 July 2010 (UTC)

Surely there should be a lot more in Criticism than there currently is. The only item in there at the moment has more to do with IIS than ASP.NET, but there are plenty of criticisms regularly levelled against ASP.NET - the viewstate becoming ridiculousy huge, the javascript requirement for many of the controls, the way it messess around with your HTML id's, the fact that even basic validation is done on the server, loss of control over the source, the noticable delay when doing a first compile, relatively high server requirements, the desktop style model is actually rather unsuitable for most websites, and the fact that many of the methods pushed by Microsoft are only required due to this odd development style in the first place. Of course, some of these thins are more of a problem with the way Visual Studo handles ASP.NET solutions, but that hasn't seemed to have stopped anyone using such things as supposed benefits. Half of the benefits listed are only benefits if you don't know how to do it yourself in the firs place. Also, you can get around many of these problems by not using feature X or Y, but if you have to do that for most of the features, you have to ask if you're using the right tchnologies in the first place. Horribly unbalanced shill articles like this are why no-one believes anything they read on Wiki any more. —Preceding unsigned comment added by 94.5.13.206 (talk) 12:34, 22 November 2010 (UTC)

"Rendering Technique" section is terrible.
I defy anybody to tell me what this means:

"ASP.NET uses a visited composites rendering technique. During compilation, the template (.aspx) file is compiled into initialization code which builds a control tree (the composite) representing the original template. Literal text goes into instances of the Literal control class, and server controls are represented by instances of a specific control class. The initialization code is combined with user-written code (usually by the assembly of multiple partial classes) and results in a class specific for the page. The page doubles as the root of the control tree." —Preceding unsigned comment added by 74.176.210.68 (talk) 03:28, 16 May 2011 (UTC)

"Examples Inline Code" Vandalism
Someone with the IP address 117.201.97.210 of the example code on the page. I would revert this change but I'm not sure how to do it without affecting any other edits made to the article after that edit. aidilfbk (talk) 13:40, 5 December 2011 (UTC)
 * Thanks for the warning. I just removed it. --Enric Naval (talk) 15:30, 5 December 2011 (UTC)

History Section Out of Date
The "History" section seems wildly out of date; it ends in 2003, before the release of ASP.NET 2.0. Moraleboost (talk) 04:05, 1 December 2012 (UTC)

Features of asp.net
It provide GUI(graphical user interface) environment for user to design attractive webform — Preceding unsigned comment added by Anshu256 (talk • contribs) 11:52, 3 November 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified one external link on ASP.NET. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20071014005507/http://www.extremeexperts.com/Net/Articles/ViewState.aspx to http://www.extremeexperts.com/Net/Articles/ViewState.aspx

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 10:10, 14 January 2018 (UTC)