error when moving a vs 2005 precompiled site to test server

[eswanson]

I have a site that has multiple web site projects. I got it working on my
windows xp sp2 computer in pre-compiled mode.

I created a new site on a windows 2003 server and copied the pre-compiled
site up to this server.

Now I am getting the following error:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The file '/RA_Log_In.aspx' has not been pre-compiled, and cannot be
requested.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.

Exception Details: System.Web.HttpException: The file '/RA_Log_In.aspx' has
not been pre-compiled, and cannot be requested.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:
[HttpException (0x80004005): The file '/RA_Log_In.aspx' has not been
pre-compiled, and cannot be requested.]

System.Web.Compilation.BuildManager.GetVPathBuildR esultInternal(VirtualPath
virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean
allowBuildInPrecompile) +3369638

System.Web.Compilation.BuildManager.GetVPathBuildR esultWithNoAssert(HttpContext
context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp,
Boolean allowBuildInPrecompile) +93

System.Web.Compilation.BuildManager.GetVirtualPath ObjectFactory(VirtualPath
virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
+111

System.Web.Compilation.BuildManager.CreateInstance FromVirtualPath(VirtualPath
virtualPath, Type requiredBaseType, HttpContext context, Boolean
allowCrossApp, Boolean noAssert) +54
System.Web.UI.PageHandlerFactory.GetHandlerHelper( HttpContext context,
String requestType, VirtualPath virtualPath, String physicalPath) +31

System.Web.UI.PageHandlerFactory.System.Web.IHttpH andlerFactory2.GetHandler(HttpContext
context, String requestType, VirtualPath virtualPath, String physicalPath) +40
System.Web.HttpApplication.MapHttpHandler(HttpCont ext context, String
requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
+139

System.Web.MapHandlerExecutionStep.System.Web.Http Application.IExecutionStep.Execute() +120
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously) +155
What can I do to correct this error? What is the cause of the this error?

Thanks

Eric

[Peter Bromberg [C# MVP]]

Eric,
With a precompiled web, all the Aspx files are just 86 byte "Stubs" - there
is a precompiled assembly in the /bin folder to match it. Sounds like you
have different settings in your different projects, or that you may have
identical items in more than one project one of which is overwriting a
previous one.
You could try checking the "Make this precompiled web updateable" checkbox
when you perform your Publish operation. Or, you could switch to the new Web
Deployment Project add-in which is more like VS.NET 2003.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"eswanson" wrote:

I have a site that has multiple web site projects. I got it working on my
windows xp sp2 computer in pre-compiled mode.

I created a new site on a windows 2003 server and copied the pre-compiled
site up to this server.

Now I am getting the following error:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The file '/RA_Log_In.aspx' has not been pre-compiled, and cannot be
requested.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.

Exception Details: System.Web.HttpException: The file '/RA_Log_In.aspx' has
not been pre-compiled, and cannot be requested.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:
[HttpException (0x80004005): The file '/RA_Log_In.aspx' has not been
pre-compiled, and cannot be requested.]

System.Web.Compilation.BuildManager.GetVPathBuildR esultInternal(VirtualPath
virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean
allowBuildInPrecompile) +3369638

System.Web.Compilation.BuildManager.GetVPathBuildR esultWithNoAssert(HttpContext
context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp,
Boolean allowBuildInPrecompile) +93

System.Web.Compilation.BuildManager.GetVirtualPath ObjectFactory(VirtualPath
virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
+111

System.Web.Compilation.BuildManager.CreateInstance FromVirtualPath(VirtualPath
virtualPath, Type requiredBaseType, HttpContext context, Boolean
allowCrossApp, Boolean noAssert) +54
System.Web.UI.PageHandlerFactory.GetHandlerHelper( HttpContext context,
String requestType, VirtualPath virtualPath, String physicalPath) +31

System.Web.UI.PageHandlerFactory.System.Web.IHttpH andlerFactory2.GetHandler(HttpContext
context, String requestType, VirtualPath virtualPath, String physicalPath) +40
System.Web.HttpApplication.MapHttpHandler(HttpCont ext context, String
requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
+139

System.Web.MapHandlerExecutionStep.System.Web.Http Application.IExecutionStep.Execute() +120
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously) +155
What can I do to correct this error? What is the cause of the this error?

Thanks

Eric

[eswanson]

I did more testing last night and found out this only works if you precompile
with updates turned on.

Using the merge tool, I found that updates need to be turned on. Why when
updates are turned on, the .precompiled files in the bin directory disappear,
but when the updates are turned off, the files appear?

Thanks

Eric

"Peter Bromberg [C# MVP]" wrote:

Eric,
With a precompiled web, all the Aspx files are just 86 byte "Stubs" - there
is a precompiled assembly in the /bin folder to match it. Sounds like you
have different settings in your different projects, or that you may have
identical items in more than one project one of which is overwriting a
previous one.
You could try checking the "Make this precompiled web updateable" checkbox
when you perform your Publish operation. Or, you could switch to the new Web
Deployment Project add-in which is more like VS.NET 2003.
Peter

--
Co-founder, Eggheadcafe.com developer portal:
http://www.eggheadcafe.com
UnBlog:
http://petesbloggerama.blogspot.com


"eswanson" wrote:

I have a site that has multiple web site projects. I got it working on my
windows xp sp2 computer in pre-compiled mode.

I created a new site on a windows 2003 server and copied the pre-compiled
site up to this server.

Now I am getting the following error:

Server Error in '/' Application.
--------------------------------------------------------------------------------

The file '/RA_Log_In.aspx' has not been pre-compiled, and cannot be
requested.
Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information about
the error and where it originated in the code.

Exception Details: System.Web.HttpException: The file '/RA_Log_In.aspx' has
not been pre-compiled, and cannot be requested.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:
[HttpException (0x80004005): The file '/RA_Log_In.aspx' has not been
pre-compiled, and cannot be requested.]

System.Web.Compilation.BuildManager.GetVPathBuildR esultInternal(VirtualPath
virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean
allowBuildInPrecompile) +3369638

System.Web.Compilation.BuildManager.GetVPathBuildR esultWithNoAssert(HttpContext
context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp,
Boolean allowBuildInPrecompile) +93

System.Web.Compilation.BuildManager.GetVirtualPath ObjectFactory(VirtualPath
virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert)
+111

System.Web.Compilation.BuildManager.CreateInstance FromVirtualPath(VirtualPath
virtualPath, Type requiredBaseType, HttpContext context, Boolean
allowCrossApp, Boolean noAssert) +54
System.Web.UI.PageHandlerFactory.GetHandlerHelper( HttpContext context,
String requestType, VirtualPath virtualPath, String physicalPath) +31

System.Web.UI.PageHandlerFactory.System.Web.IHttpH andlerFactory2.GetHandler(HttpContext
context, String requestType, VirtualPath virtualPath, String physicalPath) +40
System.Web.HttpApplication.MapHttpHandler(HttpCont ext context, String
requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
+139

System.Web.MapHandlerExecutionStep.System.Web.Http Application.IExecutionStep.Execute() +120
System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean&
completedSynchronously) +155
What can I do to correct this error? What is the cause of the this error?

Thanks

Eric

[Steven Cheng[MSFT]]

Hi Eric,

Yes, this is the expected behavior. For those xxxx.compiled files, there
will occur many such files when we turn off "updatable", this is because
when turn on updatable, the ASP.NET pages (or ascx user controls) are
completely precompiled, even the aspx or ascx template file will not
contain any code or markup content(you can open the aspx/ascx file to
verify this), they're just a placeholder in such scenario. Then, at
runtime, when an aspx page is requested, how can the runtime locate the
page's actual page class/handler? This is just recorded in the
xxxx.compiled file, you can open it in text editor (it's of XML format) to
view its content. And when we turn on "updatable" in precompilation,
since the aspx/ascx file still contains the markup content and @Page
directives, the runtime can correctly find the page or other referenced
classes through the @Page or any other directives.

Hope this helps.

Regards,

Steven Cheng
Microsoft Online Support

Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)