Your problem is that you're not appreciating that javascript runs on the client using the rendered html, and what you see in visual studio aspx files is not what is rendered to the client. .net will change your control IDs so if you refer to IDs in your js you need to use the ClientID property of the control to get the proper ID, or use static ids if that is suitable (it won't always be); ASP.NET 4.0 Client ID Feature[^] Other things you need to bear in mind are code paths and how you refer to your js files in relation to your other files. There is no single trick to this, it mainly involves having a good understanding of the framework and using best practises in your coding, and tackling individual problems as you encounter them.

The answer to this is, try them out. Measure their performance for the use cases you have in mind. Your question is far too simplistic to make a reasonable judgement because performance could vary wildly for different use cases. Apart from anything else, you'll need to take into account features such as scaling out the application, how load balancing affects your app, does different parts introduce bottlenecks, as well as defining what acceptable performance is.

Hi I agree with you completely , what I normally do is put my viewstate in a session to avoid the big back and forth , and if you read my posts you'll find that they are completely pro ASP.Net over MVC All I am saying is if you are hell bend on squeezing the very last bit of performance out of your app MVC would be the way to go (it would take you way longer to code and you'll most likely get lazy debugging front end code and just start implementing bad practices) but I still prefer ASP.NET using N-Tier Architecture and good practices over MVC any day Chona1171 Web Developer (C#), Silverlight

This happens when the code you are trying to view does not exist in your project. Here[^] is a CP question answered that can help you.

You'll encounter two issues if you use Stored Procedures with MVC, but both are convenience items. 1. If you want to scaffold controllers for RAD, you will not be able to do so using a SqlConnection; MVC uses Entity Framework for this. 2. If you do not map your Stored Procedure to a model class, you will not be able to scaffold views. Again, this just affects RAD options.