Back to Community Threads
1
Issue referencing DocumentUltimate when building with optimizeCompliation.
Problem reported by Jacob Van Brunt - 6/18/2018 at 10:42 AM
Resolved
We are currently implementing DocumentUltimate in our core product. We are use optimizeCompliation in our web config to speed up our development process. When building out product in our dev environment we experience a run time exception :
 
Object reference not set to an instance of an object.
 
   at GleamTech.AspNet.UI.ComponentStateManager.SaveState(String stateId, ComponentState state)
   at GleamTech.AspNet.UI.ComponentRenderer.SaveState(StatefulComponent statefulComponent, String requestPath)
   at GleamTech.AspNet.WebForms.StatefulComponentControl`1.OnPreRender(EventArgs e)
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Control.PreRenderRecursiveInternal()
   at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
If we remove optimizeCompliation, clean, and rebuild. The solution works no problem. Is there any idea why this may be happening? Any input would be great. 

1 Reply

Reply to Thread
0
Cem Alacayir Replied
6/19/2018 at 11:26 AM
Employee Post
I could not replicate the error when debugging in Visual Studio with this setting in Web.config:
 
<compilation optimizeCompilations="true">
From the error, I guess somehow HttpContext comes as null. It may be because at runtime Asp.Net references an out of date DLL in the "Temporary ASP.NET Files" folder.
 
Please follow the steps here to clean up the "Temporary ASP.NET Files" folder.
Back to Community Threads

Reply to Thread