In an Asp.net MVC application I'd like to encapsulate the ugly wrapper code (just a literal html opening string and another closing string) we use to make corners and shadows compatible with older browsers (we don't use javascript for performance reasons) in a manner compatible with the visual studio design view.
I'd like to put the wrapper divs in a control so that I can use them in a .aspx view page and not have to look at all the mess required to make fancy corners & shadows but still get the benefit of seeing the results in the designer.
//open wrapper literal actual content //close wrapper literal
I couldn't figure out how to inject content inside 1 control and have the results visible in the designer the way master pages do, so I'm testing a system using 2 controls containing the literal html.
example usage - 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 renders properly in all browsers when I run the application but the designer seems to be confused by the fact that one control opens the divs and another closes them and renders junk. The System.Web.Mvc.ViewUserControls I'm using contain nothing but literal html, and I've replicated the behavior with several different standard style & div configurations so I'm stumped as to what is confusing the designer.
I'd like to keep the solution really simple because this is mainly a convenience setup and not worth a lot of added complexity. Any ideas?