Oxygene ASP.NET app - trouble publishing

I’ve written an ASP.NET application which runs fine in the IDE/debugger. I decided to publish it on my local web server so users could test it before publishing it on a live server.

To make a long story short, i got it published, but soon was shown the ‘Oxygene is not a supported language’ error in the browser. I did a quick search on this and found several postings saying to put it compiled, and uncheck the ‘updatable’ option. I did this, did a rebuild, and copied up the files again…and I still get this error message?

I found another message about copying the Oxygene DLLs to the server also, but now i’m an exception which appears to be coming from the compiler itself, and not from my code. Here is what it looks like:

=========================================================================
Object reference not set to an instance of an object.
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.NullReferenceException: Object reference not set to an instance of an object.

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:

[NullReferenceException: Object reference not set to an instance of an object.]
G.w…ctor(w A) +5570
C.w…ctor(q A, Boolean a) +512
C.w…ctor(q A) +39
RemObjects.Oxygene.MSBuild.OxygeneCompiler.Execute() +1515
A.N.A(CompilerParameters A, String[] a) +3739
A.N.FromFileBatch(CompilerParameters A, String[] a) +364
System.CodeDom.Compiler.CodeCompiler.System.CodeDom.Compiler.ICodeCompiler.CompileAssemblyFromFileBatch(CompilerParameters options, String[] fileNames) +196
System.CodeDom.Compiler.CodeDomProvider.CompileAssemblyFromFile(CompilerParameters options, String[] fileNames) +25
System.Web.Compilation.AssemblyBuilder.Compile() +961
System.Web.Compilation.BuildProvidersCompiler.PerformBuild() +222
System.Web.Compilation.ApplicationBuildProvider.GetGlobalAsaxBuildResult(Boolean isPrecompiledApp) +9118854
System.Web.Compilation.BuildManager.CompileGlobalAsax() +44
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +265

[HttpException (0x80004005): Object reference not set to an instance of an object.]
System.Web.Compilation.BuildManager.ReportTopLevelCompilationException() +62
System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled() +421
System.Web.Compilation.BuildManager.CallAppInitializeMethod() +31
System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException) +691

[HttpException (0x80004005): Object reference not set to an instance of an object.]
System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +9090876
System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +97
System.Web.HttpRuntime.ProcessRequestInternal(HttpWorkerRequest wr) +258


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

======================================================================

Any suggestions as to how to track down this exception?

I’m using version 5.2.37.1071 of Oxygene for .NET in VS 2012 Pro.

My web server is running IIS 6 on Windows server 2003.

Any help appreciated!

Alan

Instead of copying the Oxygene DLL’s, download the free command line compiler (http://www.remobjects.com/downloads.aspx) and install it on the server.

I publish not “updatable” Web Sites all the time for use with Silverlight. Not a problem here. Maybe your original published code is cached so the new no updatable one isn’t being loaded?

And I am using web Site project and NOT web Application project.

But, it should work.

Of course, I don’t have any Pascal code in the page code behind. Maybe that is the difference. I don’t know. I only do Silverlight.