[Mono-bugs] [Bug 53171][Min] New - System.Web.Compilation - compiler execution problem

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by jaak@zd.com.pl.

http://bugzilla.ximian.com/show_bug.cgi?id=53171

--- shadow/53171	2004-01-21 10:33:15.000000000 -0500
+++ shadow/53171.tmp.3255	2004-01-21 10:33:15.000000000 -0500
@@ -0,0 +1,74 @@
+Bug#: 53171
+Product: Mono/Class Libraries
+Version: unspecified
+OS: 
+OS Details: 
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Minor
+Component: Sys.Web
+AssignedTo: mono-bugs@ximian.com                            
+ReportedBy: jaak@zd.com.pl               
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: System.Web.Compilation - compiler execution problem
+
+This applies to CVS as of 21 Jan 2004:
+
+Description of Problem:
+
+Looks like the System.Web.Compilation attempts to spawn the compiler
+without specifying full path (e.g. "mcs" instead of "/opt/mono/bin/mcs").
+This causes problems when "mcs" is not in the path. 
+
+Steps to reproduce the problem:
+
+1. Install mono,mcs,xsp,mod_mono in /opt/mono (or some other path)
+2. Run /opt/mono/bin/mono /opt/mono/bin/mod-mono-server.exe <parameters
+here> (note that /opt/mono/bin is not in the path)
+3. Navigate to one of the *.aspx pages
+
+Actual Results:
+
+System.ComponentModel.Win32Exception: Cannot find the specified file
+in <0x00310> System.Diagnostics.Process:Start_common
+(System.Diagnostics.ProcessStartInfo,System.Diagnostics.Process)
+in <0x00016> System.Diagnostics.Process:Start ()
+in <0x0005d> (wrapper remoting-invoke-with-check)
+System.Diagnostics.Process:Start ()
+in <0x00204> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromFileBatch
+(System.CodeDom.Compiler.CompilerParameters,string[],bool)
+in <0x00326> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDomBatch
+(System.CodeDom.Compiler.CompilerParameters,System.CodeDom.CodeCompileUnit[])
+in <0x00060> Mono.CSharp.CSharpCodeCompiler:CompileAssemblyFromDom
+(System.CodeDom.Compiler.CompilerParameters,System.CodeDom.CodeCompileUnit)
+in <0x00133> System.Web.Compilation.CachingCompiler:Compile
+(System.Web.Compilation.BaseCompiler)
+in <0x00263> System.Web.Compilation.BaseCompiler:GetCompiledType ()
+in <0x00137> System.Web.Compilation.AspGenerator:GetCompiledType ()
+in <0x0003b> System.Web.UI.PageParser:CompileIntoType ()
+in <0x00025> System.Web.UI.TemplateControlParser:GetCompiledInstance ()
+in <0x00051> System.Web.UI.PageParser:GetCompiledPageInstance
+(string,string,System.Web.HttpContext)
+in <0x00013> System.Web.UI.PageHandlerFactory:GetHandler
+(System.Web.HttpContext,string,string,string)
+in <0x001b4> System.Web.HttpApplication:CreateHttpHandler
+(System.Web.HttpContext,string,string,string)
+in <0x0011f> .CreateHandlerState:Execute ()
+in <0x00084> .StateMachine:ExecuteState
+(System.Web.HttpApplication/IStateHandler,bool&)
+
+Expected Results:
+No compilation error.
+
+How often does this happen? 
+Every time.
+
+Additional Information:
+
+Executing the following command before spawning "mod-mono-server.exe" helps:
+
+export PATH=/opt/mono/bin:$PATH