visual studio debug fatal error 0x8007000e with .NET 4.5 while debugging .NET 4.0 application

9

After installing VS2012 and .NET 4.5 both Visual Studio 2010 and 2012 started hanging when debugging our application with a fatal error 0x8007000e. I know this error means the process is out of memory and I can see on task manager the devenv.exe process memory growing until it reaches the 3GB limit. At this point the exception occurs.

On the machines that don't have .Net 4.5 everything works fine. Our application is built in .Net 4.0 and migrating to .Net 4.5 it is not an option. Is there any workaround for this? We would like to start using VS2012 but we can’t migrate all of our applications for .Net 4.5.

Thanks for the help,

Nuno Pereira

visual-studio
.net-4.0
.net-4.5
fatal-error
asked on Stack Overflow Nov 19, 2012 by nflash

2 Answers

4

If you run under .NET 4.5 framework, but compile in .NET 4, you might want to try adding this to your config file:

<configuration>
  <system.xml.serialization>
    <xmlSerializer useLegacySerializerGeneration="true"/>
  </system.xml.serialization>
</configuration>

As suggested to me in this link:

Serialization breaks in .NET 4.5

answered on Stack Overflow Feb 5, 2013 by omer schleifer • edited May 23, 2017 by Community
3

I've received feedback from Kevin Halverson about this issue. It seems that it is related to XmlSerialization. Generating static serialization assembly prevents the error from happening. Static serialization assembly can be generated using ‘sgen.exe’, ‘svcutil.exe /t:xmlSerializer’ or by turning on the ‘generate serialization assembly’ option on the project’s properties in Visual Studio.

Thanks to Anand and Kevin for all the help.

answered on Stack Overflow Jan 22, 2013 by nflash

User contributions licensed under CC BY-SA 3.0