I ran across a strange error while deploying a very simple DLL. It contained only one class; a web services proxy class to the Lists SharePoint web service that I generated using the wsdl tool. Here is the error:
Unable to generate a temporary class (result=1).
error CS2001: Source file ‘C:\WINDOWS\TEMP_zm3ve2y.0.cs’ could not be found
error CS2008: No inputs specified
Apparently, this is because the generated proxy class uses XmlSerializer somewhere internally. My guess is that it is de-serializing the soap messages into objects?
Some googling turned up the common answer of “just give the account access to the temp directory.” This seemed strange to me (also something our infrastructure team was wary of doing). Eventually I found this awesome answer by Richard. Essentially your options are:
- Give the account access to the temp directory
- Use the sgen tool to pre-generate the serialization assembly
- Not use the proxy class (??)
In my opinion, using sgen is the logical choice. The documentation for sgen also puts it pretty clearly:
When the XML Serializer Generator is not used, a XmlSerializer generates serialization code and a serialization assembly for each type every time an application is run. To improve the performance of XML serialization startup, use the Sgen.exe tool to generate those assemblies the assemblies in advance. These assemblies can then be deployed with the application.
So all I needed to do was run this command against the Release version of my DLL:
sgen /a:MyAssembly.dll /compiler:/keyfile:../../MyAssembly.snk
This will generate another assembly: MyAssembly.XmlSerializers.dll. Cool!