Re: Re: System.IO.FileNotFoundException error after splitting one dll into two
From: Elena Kharitidi (elenak_at_online.microsoft.com)
Date: 09/01/04
- Next message: Pepe: "DiscoCodeGenerator unable to initialize code generator"
- Previous message: Elena Kharitidi: "RE: Parsing WSDL and System.Web.Services.Description"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 01 Sep 2004 19:25:41 GMT
there are a couple of reasons for the exception
1. the account that user code runs under does not have enough permissions
to read and write to the process temp directory: The XmlSerializer
generates and compiles code on the fly to do serialization and
deserialization. It uses CodeDom to do the compilation and a side effect
of code dom compilation is the use of temporary files on disk (at least for
c#). Whatever user the process is running as must have full access to
that dir. On the server-side this means that the asp.net worker process
account must have access (unless you’re doing impersonation, in which case
the impersonated user must have access).
2. there are compile errors in the XmlSerializer generated code
to see tht detail output (errors generated by the compiler) you need to add
a switch to the machine.config to keep compiler generated files:
<system.diagnostics>
<switches>
<add name="XmlSerialization.Compilation" value="4"/>
</switches>
</system.diagnostics>
now take a look at the %temp% (%windows%\temp on the server side) dir it
should have the _tmpname.00.cs, _tmpname.out and _tmpname.err files, the
cs file is the generated source, the *.out and the *.err files will have
details.
- Next message: Pepe: "DiscoCodeGenerator unable to initialize code generator"
- Previous message: Elena Kharitidi: "RE: Parsing WSDL and System.Web.Services.Description"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
