tag:blogger.com,1999:blog-6979072578516949047.post216037084272749769..comments2010-01-12T23:12:03.353-07:00That One Guyhttp://www.blogger.com/profile/06960050789221425916noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-6979072578516949047.post-60921384077378475972010-01-12T23:10:04.397-07:002010-01-12T23:10:04.397-07:00Worked for me, ThanksNaganand Mavnurnoreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-78306483551850900192009-10-29T14:11:42.845-06:002009-10-29T14:11:42.845-06:00Nice! I&#39;m so glad this is working for everyone.<br /><br />I&#39;ve since discovered that this problem occurs if you edit the ASPX page in regards to adding/modifing/deleting ASP.NET controls in the ASPX page while debugging the site. If you make minor tweaks like attribute changes or style tweaks, etc, you shouldn&#39;t see the error.<br /><br />The behavior is due to the magic of Visual Studio dynamically updating that designer file on-the-fly as you make ASP.NET control-releated changes; it just doesn&#39;t seem to handle it well if you&#39;re making those changes while in debug mode.<br /><br />If you simply stop debugging after getting the error, add/delete the character in the offending designer.cs and save, then rebuild, you should be golden every time.<br /><br />So for future reference, to avoid seeing the error, try not to tweak ASP.NET controls in your ASPX pages while debugging. If you forget, you know how to fix it.<br /><br />Happy coding!That One Guyhttp://www.blogger.com/profile/06960050789221425916noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-87504360752176784912009-10-29T12:57:23.573-06:002009-10-29T12:57:23.573-06:00Thanks for this solution! I too didn&#39;t feel comfortable deleting the designer file then converting the project to a web application. Your solution worked perfectly for me the first time and I didn&#39;t clean the solution or do anything else prior to attempting it.Bob C.noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-20805631451614418802009-10-02T09:31:19.466-06:002009-10-02T09:31:19.466-06:00thx a lot!Sheyhttp://www.blogger.com/profile/13927835770584066228noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-84187792778774033122009-09-08T12:37:23.713-06:002009-09-08T12:37:23.713-06:00I definitely like this solution best. Thanks for the suggestion!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-1890337802330454492009-05-28T15:25:22.078-06:002009-05-28T15:25:22.078-06:00I've also noticed that this happens sometimes when you're editing markup in a page/control (in my case a MasterPage) while debugging.<br /><br />After stopping debug, completing my edits, going into the designer.cs, adding/deleting the character and saving again, the error went away.<br /><br />(Again in Visual Studio 2008; not sure if you have to do it the hard way in 2005 as mentioned in the prior comment.)That One Guyhttp://www.blogger.com/profile/06960050789221425916noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-74486052001705726662009-05-28T06:10:13.580-06:002009-05-28T06:10:13.580-06:00I use Visual Studio 2005 and I had to delete the .designer.cs file and then right click on the aspx file and choose "Create Web Application" as per 1 of the comments in http://www.hanselman.com/blog/ErrorConnectingToUndoManagerOfSourceFileQuotwhateverDesignerquot.aspxAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-19791740670635479582009-05-07T23:50:00.000-06:002009-05-07T23:50:00.000-06:00@reeta: I'm glad it worked for you too! Were you able to fix it without cleaning the solution?That One Guyhttp://www.blogger.com/profile/06960050789221425916noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-7025240794734717342009-05-07T22:42:00.000-06:002009-05-07T22:42:00.000-06:00Heaps thanks for such a simple solution.reetahttp://www.blogger.com/profile/15030310174047303052noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-53527916153009543142009-03-25T08:36:00.000-06:002009-03-25T08:36:00.000-06:00@Anonymous:<BR/>Sweet! I'm glad we could help. It is incredibly annoying when that happens. :)That One Guyhttp://www.blogger.com/profile/06960050789221425916noreply@blogger.comtag:blogger.com,1999:blog-6979072578516949047.post-45932270708381716252009-03-25T07:48:00.000-06:002009-03-25T07:48:00.000-06:00Rock on! This was the only thing that worked for me after trying several of the other suggestions!Anonymousnoreply@blogger.com