views:

47

answers:

0

I have a build process using the sgen.exe tool to build Xmlserializer assemblies to optimize their use in a WinForms application. This application was originally written on the .NET 2.0 framework and after updating our server to have the 3.5sp1 framework the calls to Sgen error out with an AccessViolation exception.

See the call below:

C:\SVS\Release>"C:\Program Files\Microsoft Visual Studio 8\SDK\v2.0\Bin\sgen" /p /compiler:/keyfile:c:\protector\MyApp.snk CoreServices.dll /force

Microsoft (R) Xml Serialization support utility [Microsoft (R) .NET Framework, Version 2.0.50727.42] Copyright (C) Microsoft Corporation. All rights reserved. Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. at SgenTool.Sgen.Error(Exception e, String prefix, Boolean parsableerrors) at SgenTool.Sgen.Run(String[] args) at SgenTool.Sgen.Main(String[] args)

I've tried to remove the key signing step and it makes no difference. The CoreServices.dll exists but sgen doesn't like it anymore.

Any ideas anyone?