Showing posts with label compilation. Show all posts
Showing posts with label compilation. Show all posts

Wednesday, March 28, 2012

The compiler failed with error code -1073741502.

Any ideals what would cause this ?

Compilation Error
Description: An error occurred during the compilation of a resource
required to service this request. Please review the following specific
error details and modify your source code appropriately.

Compiler Error Message: The compiler failed with error code
-1073741502.

Show Detailed Compiler Output:

C:\WINDOWS\system32"c:\windows\microsoft.net\framework
\v1.1.4322\csc.exe" /t:library /utf8output /R:"c:\windows\microsoft.net
\framework\v1.1.4322\mscorlib.dll" /R:"c:\windows\microsoft.net
\framework\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\g8avop1s.dll" /R:"c:\windows\assembly\gac
\system.enterpriseservices\1.0.5000.0__b03f5f7f11d 50a3a
\system.enterpriseservices.dll" /R:"c:\windows\microsoft.net\framework
\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\assembly\dl2\9b87984c
\00665a14_66a1c201\interop.wmencagentlocatorlib.dl l" /R:"c:\windows
\assembly\gac\system.data
\1.0.5000.0__b77a5c561934e089\system.data.dll" /R:"c:\windows
\microsoft.net\framework\v1.1.4322\temporary asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly
\dl2\a9191987\00665a14_66a1c201\interop.wmencagtli b.dll" /R:"c:\windows
\assembly\gac\system.web.mobile\1.0.5000.0__b03f5f 7f11d50a3a
\system.web.mobile.dll" /R:"c:\windows\microsoft.net\framework
\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\assembly
\dl2\8656e736\0009e65d_74d4c701\log4net.dll" /R:"c:\windows
\microsoft.net\framework\v1.1.4322\temporary asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly\dl 2\e0eb1a8b
\00bdaa62_74d4c701\cnnencodingservices.dll" /R:"c:\windows\assembly\gac
\system.drawing\1.0.5000.0__b03f5f7f11d50a3a\syste m.drawing.dll" /R:"c:
\windows\microsoft.net\framework\v1.1.4322\tempora ry asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly
\dl2\ebf89319\00dcb45c_74d4c701\wmewebsvcagent.dll " /R:"c:\windows
\assembly\gac\system.xml\1.0.5000.0__b77a5c561934e 089\system.xml.dll" /
R:"c:\windows\microsoft.net\framework\v1.1.4322\tempo rary asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly
\dl2\18b641f9\00665a14_66a1c201\interop.wmencoderl ib.dll" /R:"c:
\windows\assembly\gac\system.web.services\1.0.5000 .0__b03f5f7f11d50a3a
\system.web.services.dll" /R:"c:\windows\microsoft.net\framework
\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\assembly\dl2\b9e5a82b
\00dcb45c_74d4c701\wmewebsvc.dll" /R:"c:\windows\assembly\gac\system
\1.0.5000.0__b77a5c561934e089\system.dll" /R:"c:\windows\assembly\gac
\system.web\1.0.5000.0__b03f5f7f11d50a3a\system.we b.dll" /out:"C:
\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Tempora ry ASP.NET Files
\cnnencodingservices\0f9adc62\70fb5ce7\hic1jo5y.dl l" /D:DEBUG /debug+ /
optimize- /warnaserror /w:1 "C:\WINDOWS\Microsoft.NET\Framework
\v1.1.4322\Temporary ASP.NET Files\cnnencodingservices
\0f9adc62\70fb5ce7\hic1jo5y.0.cs"

Show Complete Compilation Source:

Line
1: //------------------------
Line 2: // <autogenerated>
Line 3: // This code was generated by a tool.
Line 4: // Runtime Version: 1.1.4322.2032
Line 5: //
Line 6: // Changes to this file may cause incorrect behavior
and will be lost if
Line 7: // the code is regenerated.
Line 8: // </autogenerated>
Line
9: //------------------------
Line 10:
Line 11: namespace ASP {
Line 12: using System;
Line 13: using System.Collections;
Line 14: using System.Collections.Specialized;
Line 15: using System.Configuration;
Line 16: using System.Text;
Line 17: using System.Text.RegularExpressions;
Line 18: using System.Web;
Line 19: using System.Web.Caching;
Line 20: using System.Web.SessionState;
Line 21: using System.Web.Security;
Line 22: using System.Web.UI;
Line 23: using System.Web.UI.WebControls;
Line 24: using System.Web.UI.HtmlControls;
Line 25: using ASP;
Line 26:
Line 27: #line 2 "c:\windows\microsoft.net\framework
\v1.1.4322\Config\DefaultWsdlHelpGenerator.aspx"
Line 28: using System.IO;
Line 29:
Line 30: #line default
Line 31: #line hidden
Line 32:
Line 33: #line 3 "c:\windows\microsoft.net\framework
\v1.1.4322\Config\DefaultWsdlHelpGenerator.aspx"
Line 34: using System.Xml.Serialization;you had the app running while you were trying to build it. Not going to
happen. Close down the web app first then try and build it again.

<rkcons@dotnet.itags.org.gmail.comwrote in message
news:1190212403.368282.126580@dotnet.itags.org.57g2000hsv.googlegro ups.com...

Quote:

Originally Posted by

Any ideals what would cause this ?
>
>
Compilation Error
Description: An error occurred during the compilation of a resource
required to service this request. Please review the following specific
error details and modify your source code appropriately.
>
Compiler Error Message: The compiler failed with error code
-1073741502.
>
>
>
Show Detailed Compiler Output:
>
C:\WINDOWS\system32"c:\windows\microsoft.net\framework
\v1.1.4322\csc.exe" /t:library /utf8output /R:"c:\windows\microsoft.net
\framework\v1.1.4322\mscorlib.dll" /R:"c:\windows\microsoft.net
\framework\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\g8avop1s.dll" /R:"c:\windows\assembly\gac
\system.enterpriseservices\1.0.5000.0__b03f5f7f11d 50a3a
\system.enterpriseservices.dll" /R:"c:\windows\microsoft.net\framework
\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\assembly\dl2\9b87984c
\00665a14_66a1c201\interop.wmencagentlocatorlib.dl l" /R:"c:\windows
\assembly\gac\system.data
\1.0.5000.0__b77a5c561934e089\system.data.dll" /R:"c:\windows
\microsoft.net\framework\v1.1.4322\temporary asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly
\dl2\a9191987\00665a14_66a1c201\interop.wmencagtli b.dll" /R:"c:\windows
\assembly\gac\system.web.mobile\1.0.5000.0__b03f5f 7f11d50a3a
\system.web.mobile.dll" /R:"c:\windows\microsoft.net\framework
\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\assembly
\dl2\8656e736\0009e65d_74d4c701\log4net.dll" /R:"c:\windows
\microsoft.net\framework\v1.1.4322\temporary asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly\dl 2\e0eb1a8b
\00bdaa62_74d4c701\cnnencodingservices.dll" /R:"c:\windows\assembly\gac
\system.drawing\1.0.5000.0__b03f5f7f11d50a3a\syste m.drawing.dll" /R:"c:
\windows\microsoft.net\framework\v1.1.4322\tempora ry asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly
\dl2\ebf89319\00dcb45c_74d4c701\wmewebsvcagent.dll " /R:"c:\windows
\assembly\gac\system.xml\1.0.5000.0__b77a5c561934e 089\system.xml.dll" /
R:"c:\windows\microsoft.net\framework\v1.1.4322\tempo rary asp.net files
\cnnencodingservices\0f9adc62\70fb5ce7\assembly
\dl2\18b641f9\00665a14_66a1c201\interop.wmencoderl ib.dll" /R:"c:
\windows\assembly\gac\system.web.services\1.0.5000 .0__b03f5f7f11d50a3a
\system.web.services.dll" /R:"c:\windows\microsoft.net\framework
\v1.1.4322\temporary asp.net files\cnnencodingservices
\0f9adc62\70fb5ce7\assembly\dl2\b9e5a82b
\00dcb45c_74d4c701\wmewebsvc.dll" /R:"c:\windows\assembly\gac\system
\1.0.5000.0__b77a5c561934e089\system.dll" /R:"c:\windows\assembly\gac
\system.web\1.0.5000.0__b03f5f7f11d50a3a\system.we b.dll" /out:"C:
\WINDOWS\Microsoft.NET\Framework\v1.1.4322\Tempora ry ASP.NET Files
\cnnencodingservices\0f9adc62\70fb5ce7\hic1jo5y.dl l" /D:DEBUG /debug+ /
optimize- /warnaserror /w:1 "C:\WINDOWS\Microsoft.NET\Framework
\v1.1.4322\Temporary ASP.NET Files\cnnencodingservices
\0f9adc62\70fb5ce7\hic1jo5y.0.cs"
>
>
>
>
>
>
>
Show Complete Compilation Source:
>
Line
1:
//------------------------
Line 2: // <autogenerated>
Line 3: // This code was generated by a tool.
Line 4: // Runtime Version: 1.1.4322.2032
Line 5: //
Line 6: // Changes to this file may cause incorrect behavior
and will be lost if
Line 7: // the code is regenerated.
Line 8: // </autogenerated>
Line
9:
//------------------------
Line 10:
Line 11: namespace ASP {
Line 12: using System;
Line 13: using System.Collections;
Line 14: using System.Collections.Specialized;
Line 15: using System.Configuration;
Line 16: using System.Text;
Line 17: using System.Text.RegularExpressions;
Line 18: using System.Web;
Line 19: using System.Web.Caching;
Line 20: using System.Web.SessionState;
Line 21: using System.Web.Security;
Line 22: using System.Web.UI;
Line 23: using System.Web.UI.WebControls;
Line 24: using System.Web.UI.HtmlControls;
Line 25: using ASP;
Line 26:
Line 27: #line 2 "c:\windows\microsoft.net\framework
\v1.1.4322\Config\DefaultWsdlHelpGenerator.aspx"
Line 28: using System.IO;
Line 29:
Line 30: #line default
Line 31: #line hidden
Line 32:
Line 33: #line 3 "c:\windows\microsoft.net\framework
\v1.1.4322\Config\DefaultWsdlHelpGenerator.aspx"
Line 34: using System.Xml.Serialization;
>

Saturday, March 24, 2012

The element 'compilation' has invalid child element 'compilers'.

I have a number of web projects converted from 1.1 to 2.0 in VS2005.
I am methodically seeing the error below:
The element 'compilation' has invalid child element 'compilers'. List of
possible elements expected: 'assemblies, buildProviders, codeSubDirectories,
expressionBuilders'.
Here's what the web config looks like. The error doesn't cause any issues
and according to the MSDN documentation this is valid. So why is VS2005
giving me this bogus error?
<configuration>
<system.web>
<httpRuntime maxRequestLength="8192"/>
<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to insert debugging symbols (.pdb
information)
into the compiled page. Because this creates a larger file that
executes
more slowly, you should set this value to true only when debugging
and to
false at all other times. For more information, refer to the
documentation about
debugging ASP.NET files.
-->
<compilation defaultLanguage="vb" debug="true" batch="false">
<compilers>
<compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"
extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
/imports:Microsoft.VisualBasic,System,System.Collections,System.Configuratio
n,System.Data,System.Drawing,System.Web,System.Web.UI,System.Web.UI.HtmlCont
rols,System.Web.UI.WebControls"/></compilers>
<assemblies>
etc, etc,In 2.0, the <compilers> section is found in machine.config,
so you don't need to place it in web.config.
Check out machine.config.comments in the .Net Framework\config dir.
The syntax has changed.
It's now in the <system.codedom> section.
See : http://msdn2.microsoft.com/en-us/library/e4hwk57e.aspx
Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Robert" <robertv@.noemail.nospam> wrote in message
news:9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com...
>I have a number of web projects converted from 1.1 to 2.0 in VS2005.
> I am methodically seeing the error below:
> The element 'compilation' has invalid child element 'compilers'. List of
> possible elements expected: 'assemblies, buildProviders, codeSubDirectorie
s,
> expressionBuilders'.
> Here's what the web config looks like. The error doesn't cause any issues
> and according to the MSDN documentation this is valid. So why is VS2005
> giving me this bogus error?
> <configuration>
> <system.web>
> <httpRuntime maxRequestLength="8192"/>
> <!-- DYNAMIC DEBUG COMPILATION
> Set compilation debug="true" to insert debugging symbols (.pdb
> information)
> into the compiled page. Because this creates a larger file that
> executes
> more slowly, you should set this value to true only when debuggin
g
> and to
> false at all other times. For more information, refer to the
> documentation about
> debugging ASP.NET files.
> -->
> <compilation defaultLanguage="vb" debug="true" batch="false">
> <compilers>
> <compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
> System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"
> extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
> /imports:Microsoft.VisualBasic,System,System.Collections,System.Configurat
ion,System.Data,System.Drawing,System.Web,System.Web.UI,System.Web.UI.HtmlCo
ntrols,System.Web.UI.WebControls"/></compilers>
> <assemblies>
> etc, etc,
>

The element compilation has invalid child element compilers.

I have a number of web projects converted from 1.1 to 2.0 in VS2005.

I am methodically seeing the error below:

The element 'compilation' has invalid child element 'compilers'. List of
possible elements expected: 'assemblies, buildProviders, codeSubDirectories,
expressionBuilders'.

Here's what the web config looks like. The error doesn't cause any issues
and according to the MSDN documentation this is valid. So why is VS2005
giving me this bogus error?

<configuration>
<system.web>
<httpRuntime maxRequestLength="8192"/>
<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to insert debugging symbols (.pdb
information)
into the compiled page. Because this creates a larger file that
executes
more slowly, you should set this value to true only when debugging
and to
false at all other times. For more information, refer to the
documentation about
debugging ASP.NET files.
-->
<compilation defaultLanguage="vb" debug="true" batch="false">
<compilers>
<compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"
extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
/imports:Microsoft.VisualBasic,System,System.Collec tions,System.Configuration,System.Data,System.Draw ing,System.Web,System.Web.UI,System.Web.UI.HtmlCon trols,System.Web.UI.WebControls"/></compilers>
<assemblies
etc, etc,In 2.0, the <compilers> section is found in machine.config,
so you don't need to place it in web.config.

Check out machine.config.comments in the .Net Framework\config dir.

The syntax has changed.
It's now in the <system.codedom> section.

See : http://msdn2.microsoft.com/en-us/library/e4hwk57e.aspx

Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
ASPNETFAQ.COM : http://www.aspnetfaq.com/
Foros de ASP.NET en Espaol : http://asp.net.do/foros/
======================================
"Robert" <robertv@.noemail.nospam> wrote in message
news:9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com...
>I have a number of web projects converted from 1.1 to 2.0 in VS2005.
> I am methodically seeing the error below:
> The element 'compilation' has invalid child element 'compilers'. List of
> possible elements expected: 'assemblies, buildProviders, codeSubDirectories,
> expressionBuilders'.
> Here's what the web config looks like. The error doesn't cause any issues
> and according to the MSDN documentation this is valid. So why is VS2005
> giving me this bogus error?
> <configuration>
> <system.web>
> <httpRuntime maxRequestLength="8192"/>
> <!-- DYNAMIC DEBUG COMPILATION
> Set compilation debug="true" to insert debugging symbols (.pdb
> information)
> into the compiled page. Because this creates a larger file that
> executes
> more slowly, you should set this value to true only when debugging
> and to
> false at all other times. For more information, refer to the
> documentation about
> debugging ASP.NET files.
> -->
> <compilation defaultLanguage="vb" debug="true" batch="false">
> <compilers>
> <compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
> System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"
> extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
> /imports:Microsoft.VisualBasic,System,System.Collec tions,System.Configuration,System.Data,System.Draw ing,System.Web,System.Web.UI,System.Web.UI.HtmlCon trols,System.Web.UI.WebControls"/></compilers>
> <assemblies>
> etc, etc,
Thanks for the response.

I removed it entirely from web.config as it is apparently unnecessary.

Guess I wish the migration wizard could of either 1) removed it for me or 2)
flagged it as a todo with an explanation.

Thx.
R-

"Juan T. Llibre" wrote:

> In 2.0, the <compilers> section is found in machine.config,
> so you don't need to place it in web.config.
> Check out machine.config.comments in the .Net Framework\config dir.
> The syntax has changed.
> It's now in the <system.codedom> section.
> See : http://msdn2.microsoft.com/en-us/library/e4hwk57e.aspx
>
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ASPNETFAQ.COM : http://www.aspnetfaq.com/
> Foros de ASP.NET en Espa?ol : http://asp.net.do/foros/
> ======================================
> "Robert" <robertv@.noemail.nospam> wrote in message
> news:9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com...
> >I have a number of web projects converted from 1.1 to 2.0 in VS2005.
> > I am methodically seeing the error below:
> > The element 'compilation' has invalid child element 'compilers'. List of
> > possible elements expected: 'assemblies, buildProviders, codeSubDirectories,
> > expressionBuilders'.
> > Here's what the web config looks like. The error doesn't cause any issues
> > and according to the MSDN documentation this is valid. So why is VS2005
> > giving me this bogus error?
> > <configuration>
> > <system.web>
> > <httpRuntime maxRequestLength="8192"/>
> > <!-- DYNAMIC DEBUG COMPILATION
> > Set compilation debug="true" to insert debugging symbols (.pdb
> > information)
> > into the compiled page. Because this creates a larger file that
> > executes
> > more slowly, you should set this value to true only when debugging
> > and to
> > false at all other times. For more information, refer to the
> > documentation about
> > debugging ASP.NET files.
> > -->
> > <compilation defaultLanguage="vb" debug="true" batch="false">
> > <compilers>
> > <compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
> > System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=B77A5C561934E089"
> > extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
> > /imports:Microsoft.VisualBasic,System,System.Collec tions,System.Configuration,System.Data,System.Draw ing,System.Web,System.Web.UI,System.Web.UI.HtmlCon trols,System.Web.UI.WebControls"/></compilers>
> > <assemblies>
> > etc, etc,
>
Hi Robert,

Yes, what a pity that the migration wizard was not able to automatically
correct this, maybe it is due to the <system.codedom> is outside the
<system.web> that beyond the migration checking. Anyway, the error message
make some sense, also thanks for Juan's informative suggestion.

Thanks,

Steven Cheng
Microsoft Online Support

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

-------
| Thread-Topic: The element 'compilation' has invalid child element
'compilers
| thread-index: AcXpe7dhGIAffoz4SzOtjdSjQDOyUA==
| X-WBNR-Posting-Host: 67.180.214.235
| From: =?Utf-8?B?Um9iZXJ0?= <robertv@.noemail.nospam>
| References: <9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com>
<ewe5xmX6FHA.3924@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: The element 'compilation' has invalid child element
'compilers
| Date: Mon, 14 Nov 2005 16:30:01 -0800
| Lines: 72
| Message-ID: <0A4CC52E-0180-414A-9D4D-DAF5F94820F1@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFT NGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet:358118
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Thanks for the response.
|
| I removed it entirely from web.config as it is apparently unnecessary.
|
| Guess I wish the migration wizard could of either 1) removed it for me or
2)
| flagged it as a todo with an explanation.
|
| Thx.
| R-
|
| "Juan T. Llibre" wrote:
|
| > In 2.0, the <compilers> section is found in machine.config,
| > so you don't need to place it in web.config.
| >
| > Check out machine.config.comments in the .Net Framework\config dir.
| >
| > The syntax has changed.
| > It's now in the <system.codedom> section.
| >
| > See : http://msdn2.microsoft.com/en-us/library/e4hwk57e.aspx
| >
| >
| >
| >
| > Juan T. Llibre, ASP.NET MVP
| > ASP.NET FAQ : http://asp.net.do/faq/
| > ASPNETFAQ.COM : http://www.aspnetfaq.com/
| > Foros de ASP.NET en Espa?ol : http://asp.net.do/foros/
| > ======================================
| > "Robert" <robertv@.noemail.nospam> wrote in message
| > news:9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com...
| > >I have a number of web projects converted from 1.1 to 2.0 in VS2005.
| | > > I am methodically seeing the error below:
| | > > The element 'compilation' has invalid child element 'compilers'.
List of
| > > possible elements expected: 'assemblies, buildProviders,
codeSubDirectories,
| > > expressionBuilders'.
| | > > Here's what the web config looks like. The error doesn't cause any
issues
| > > and according to the MSDN documentation this is valid. So why is
VS2005
| > > giving me this bogus error?
| | > > <configuration>
| > > <system.web>
| > > <httpRuntime maxRequestLength="8192"/>
| > > <!-- DYNAMIC DEBUG COMPILATION
| > > Set compilation debug="true" to insert debugging symbols
(.pdb
| > > information)
| > > into the compiled page. Because this creates a larger file
that
| > > executes
| > > more slowly, you should set this value to true only when
debugging
| > > and to
| > > false at all other times. For more information, refer to the
| > > documentation about
| > > debugging ASP.NET files.
| > > -->
| > > <compilation defaultLanguage="vb" debug="true" batch="false">
| > > <compilers>
| > > <compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
| > > System, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089"
| > > extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
| /imports:Microsoft.VisualBasic,System,System.Collec tions,System.Configuratio
n,System.Data,System.Drawing,System.Web,System.Web .UI,System.Web.UI.HtmlCont
rols,System.Web.UI.WebControls"/></compilers>
| > > <assemblies>
| | > > etc, etc,
| | | >
| >
| >
|

The element 'compilation' has invalid child element 'compilers

Thanks for the response.
I removed it entirely from web.config as it is apparently unnecessary.
Guess I wish the migration wizard could of either 1) removed it for me or 2)
flagged it as a todo with an explanation.
Thx.
R-
"Juan T. Llibre" wrote:

> In 2.0, the <compilers> section is found in machine.config,
> so you don't need to place it in web.config.
> Check out machine.config.comments in the .Net Framework\config dir.
> The syntax has changed.
> It's now in the <system.codedom> section.
> See : http://msdn2.microsoft.com/en-us/library/e4hwk57e.aspx
>
>
> Juan T. Llibre, ASP.NET MVP
> ASP.NET FAQ : http://asp.net.do/faq/
> ASPNETFAQ.COM : http://www.aspnetfaq.com/
> Foros de ASP.NET en Espa?ol : http://asp.net.do/foros/
> ======================================
> "Robert" <robertv@dotnet.itags.org.noemail.nospam> wrote in message
> news:9999C8CB-CF4F-4F1A-89A5-775753A7B124@dotnet.itags.org.microsoft.com...
>
>Hi Robert,
Yes, what a pity that the migration wizard was not able to automatically
correct this, maybe it is due to the <system.codedom> is outside the
<system.web> that beyond the migration checking. Anyway, the error message
make some sense, also thanks for Juan's informative suggestion.
Thanks,
Steven Cheng
Microsoft Online Support
Get Secure! www.microsoft.com/security
(This posting is provided "AS IS", with no warranties, and confers no
rights.)
| Thread-Topic: The element 'compilation' has invalid child element
'compilers
| thread-index: AcXpe7dhGIAffoz4SzOtjdSjQDOyUA==
| X-WBNR-Posting-Host: 67.180.214.235
| From: examnotes <robertv@.noemail.nospam>
| References: <9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com>
<ewe5xmX6FHA.3924@.TK2MSFTNGP10.phx.gbl>
| Subject: Re: The element 'compilation' has invalid child element
'compilers
| Date: Mon, 14 Nov 2005 16:30:01 -0800
| Lines: 72
| Message-ID: <0A4CC52E-0180-414A-9D4D-DAF5F94820F1@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 8bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.dotnet.framework.aspnet
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl
microsoft.public.dotnet.framework.aspnet:358118
| X-Tomcat-NG: microsoft.public.dotnet.framework.aspnet
|
| Thanks for the response.
|
| I removed it entirely from web.config as it is apparently unnecessary.
|
| Guess I wish the migration wizard could of either 1) removed it for me or
2)
| flagged it as a todo with an explanation.
|
| Thx.
| R-
|
| "Juan T. Llibre" wrote:
|
| > In 2.0, the <compilers> section is found in machine.config,
| > so you don't need to place it in web.config.
| >
| > Check out machine.config.comments in the .Net Framework\config dir.
| >
| > The syntax has changed.
| > It's now in the <system.codedom> section.
| >
| > See : http://msdn2.microsoft.com/en-us/library/e4hwk57e.aspx
| >
| >
| >
| >
| > Juan T. Llibre, ASP.NET MVP
| > ASP.NET FAQ : http://asp.net.do/faq/
| > ASPNETFAQ.COM : http://www.aspnetfaq.com/
| > Foros de ASP.NET en Espa?ol : http://asp.net.do/foros/
| > ======================================
| > "Robert" <robertv@.noemail.nospam> wrote in message
| > news:9999C8CB-CF4F-4F1A-89A5-775753A7B124@.microsoft.com...
| > >I have a number of web projects converted from 1.1 to 2.0 in VS2005.
| > >
| > > I am methodically seeing the error below:
| > >
| > > The element 'compilation' has invalid child element 'compilers'.
List of
| > > possible elements expected: 'assemblies, buildProviders,
codeSubDirectories,
| > > expressionBuilders'.
| > >
| > > Here's what the web config looks like. The error doesn't cause any
issues
| > > and according to the MSDN documentation this is valid. So why is
VS2005
| > > giving me this bogus error?
| > >
| > > <configuration>
| > > <system.web>
| > > <httpRuntime maxRequestLength="8192"/>
| > > <!-- DYNAMIC DEBUG COMPILATION
| > > Set compilation debug="true" to insert debugging symbols
(.pdb
| > > information)
| > > into the compiled page. Because this creates a larger file
that
| > > executes
| > > more slowly, you should set this value to true only when
debugging
| > > and to
| > > false at all other times. For more information, refer to the
| > > documentation about
| > > debugging ASP.NET files.
| > > -->
| > > <compilation defaultLanguage="vb" debug="true" batch="false">
| > > <compilers>
| > > <compiler language="vb" type="Microsoft.VisualBasic.VBCodeProvider,
| > > System, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=B77A5C561934E089"
| > > extension=".VB" compilerOptions="/define:Debug=True /define:Trace=True
| > >
/imports:Microsoft.VisualBasic,System,System.Collections,System.Configuratio
n,System.Data,System.Drawing,System.Web,System.Web.UI,System.Web.UI.HtmlCont
rols,System.Web.UI.WebControls"/></compilers>
| > > <assemblies>
| > >
| > > etc, etc,
| > >
| > >
| >
| >
| >
|