Currently, I am considering transitioning an outdated frameset based asp.net website to utilize master pages. However, the daunting task of updating each page to handle name mangling is what concerns me the most. The main issue lies in javascript referencing hardcoded Id's.
Is there a way for me to notify ASP.Net that I prefer not to have mangling occur for a specific content area? I would rather manage any naming conflicts myself.
Note
I am aware of the solution provided in .Net 4.0 here. My preference is for a solution that does not require waiting and must be compatible with .Net 3.5.
Update
Are there any open-source alternatives to masterpages that can serve as a temporary solution until .Net 4.0 is available? If not, is there a workaround or hack job solution to bypass the mangling issue? Thank you