In the original page there was no id on the Image control. Only it so happens there’s already another control Image1 on the page (why that is is another point of debate for another day ).
The short of it is that this is enough for the WAP codebehind engine to fail.
BTW, if you get the General Exception Failure dialog you may not be completely screwed either.They’re not generic enough to put into a control of some sort or on a master page but generic enough that they get pasted around different pages and then customized for the specific page.The big problem for me is that when I paste between pages ASP.You create new controls in markup or the designer and – they don’t show up in your code.Even though you know the control is defined on the page you’re in red squiggly hell: So now comes the dance: You’re trying to open the markup editor, make some changes. Open the designer, move something, compile try again… The problem here is that the designer file doesn’t get re-generated if you have some sort of layout error in the page.I’ve never converted a site to WAP that just worked – usually there are a few oddball pages that require manual ‘intervention’.This is a nasty problem but also one that is to a degree self-inflicted.Before trying any solution just try to remove all the error from your aspx or ascx file, as any error on the file will prevent the Visual Studio to create a designer file for you, and it might happen that none of the solution will work for you.Solution 1 : Right Click on you aspx or ascx file and select "Convert to Web Application".If by any chance you have deleted your .and you wanted to regenerate it or you wanted to update the .file when you put new controls on your page.In this post we will show you how to force the Visual Studio to regenerate your .file.