This is becoming a major barrier. Here is what I have found so far:
Just to restate the problem. Wrapped aspx controls rendered from a formbox in a standard web site give the "page not found " error IN A NEW BROWSER WINDOW .. the error shown in the above thread and repeated below. This occurs for all such controls but ONLY when the web site is deployed.
1. I noted from your reference that virtualproviders do not work when deployed to a pre-compiled site. However there is a workaround for this refere: http://sunali.com/2008/01/09/virtualpathprovider-in-precompiled-web-sites/
2. However, since virtual path providers do not apply to ASPX hosted pages, presumably this is not related. I removed all this type of code and confirmed the problem still exists.
3. I reduced the sample previously sent just to have a hosed aspx page (and no virtualpath providers). The good news is that this worked. The bad news is that this worked:)
So now i am not sure how to proceed with debugging this.
Does the error give some indication? A new window pops up with this error whenever the wrapped class is invoked?
Is there any tracing I can do to find out what is happening.
Server Error in '/TM' Application.
The resource cannot be found.
Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.
Requested URL: /tm/Route/1.88.34/ie/en-US/MacroTheme/Content.Form1.wgx
Version Information: Microsoft .NET Framework Version:2.0.50727.1434; WebGUI Version:2.0.50727.1434