In an Asp.net MVC application, I would like to encapsulate an ugly wrapper code (just a literal html opening line and another closing line) that we use so that corners and shadows are compatible with old browsers (we do not use javascript for performance reasons) according with visual design studio.
I would like to put div wrappers in the control so that I can use them on the .aspx view page and not have to look at all the clutter needed to create fancy corners and shadows, but still benefit from viewing the results in the designer.
// open wrapper literal actual content // close wrapper literal
I could not understand how to embed content inside 1 control and have results visible in the designer, as the main pages do, so I test the system using 2 controls containing the html literal.
use case - with one control opening and another closing
<ShadowBoxStart /> //contains div open tags
Hello World. This is actual content with all the nice style divs wrapped around
<ShadowBoxEnd /> //contains div close tags
This displays correctly in all browsers when I launch the application, but the constructor seems to be confused with the fact that one control opens divs and the other closes them and makes them unnecessary. The System.Web.Mvc.ViewUserControls I use contains nothing but literal html, and I replicated the behavior with several different standard div forms and configurations, so I am puzzled by what confuses the designer.
, , . ?