ASP.NET - Common Gotchas [closed]

Answer 1

Viewstate ... if you are using it ... can get out of control if you are not paying attention to it.

Answer 2

Not a pure ASP.NET thing, but ...

I was trying to use either a) nested SELECT or b) WITH clause and just could not get it to work, but people who were obviously more knowledgeable (including someone I work with) told me the syntax was fine. TURNS OUT ...

Was not able to use either of those with OLEDB.

OLEDB query to SQL Server fails

(Also, I was bit by the response.redirect() in the try ... catch 'feature' mentioned in the OP! Great thread!)

Answer 3

Having to jump through hoops to get the .ClientID property into javascript.

It'd be nice if the render phase of the lifecycle created a script that set up a var for each server control with the same name as the control that was automatically initialized to the clientID value. Or maybe have some way to easily trigger this action.

Hmm... I bet I could set up a method for this on my own via reflection.

Answer 4

Debugging is a very cool feature of ASP.Net, but as soon as you change some code in the app_code folder, you trigger a re-build of the application, leading to all sessions being lost.

This can get very annoying while debugging a website, but you can easily prevent this using the "StateServer mode" : it's just a service to start and a line to change in the web.config : refer to msdn : http://msdn.microsoft.com/en-us/library/ms178586.aspx

1. InProc mode, which stores session state in memory on the Web server. This is the default.
2. StateServer mode, which stores session state in a separate process called the ASP.NET state service. This ensures that session state is preserved if the Web application is restarted and also makes session state available to multiple Web servers in a Web farm.
3. SQL Server ...
4. Custom ...
5. Off!

Answer 5

Life cycle of custom controls does not match up perfectly with page life cycle events of same name.

Answer 6

Databound controls inside an INamingContainer control must not be placed inside templated controls such as FormView. See this bug report for an example. Since INamingContainer controls creates their own namespace for their contained controls, two-way databinding using Bind() will not work properly. But when loading the values everything will look fine (because it is done with Eval()) it is not before you try to post back the values that they will mysteriously seem to not land in the database.

This so question demonstrates the issue well: AJAX Tabcontainer inside formview not inserting values