What is the recommended replacement for ASP.Net controls in the vibrant new world of ASP.Net MVC?
In my opinion, one of the best features of ASP.Net is the ability to write server-side controls (although admittedly, the event model is terrible to deal with). If these controls are self-tuning, then they can be divided between different projects with a minimum of fuss - you just refer to the assembly where the server control is located, and lower it to aspx. The rest is in control. This is very suitable for World of Widgets and provides efficient code reuse. How can one achieve the same thing in MVC?
What interests me most is self-adjusting controls that don't return, since I appreciate that the postback model is definitely not suitable for MVC. Can they still be encapsulated in a class that can be shared across multiple MVC web projects? Or does this require a completely different mindset, where the controls should not be populated, and partial views need to be used? Is there a way to share partial views between projects?
Finally, can I use the old (no postback) server controls in MVC projects?
source
share