We have an application compiled using Visual Studio 2010 using .net 4 which parses some data files and writes the data to SQL Server. It's currently using .net 4, but was originally .net 1.0 (or 1.1, the early history's hard to get at since we've changed version control systems in the past decade).
In any case, we recently upgraded the server that it runs on to Windows 2012, and it's stopped working, giving a System.BadImageFormat exception. The same executable works fine on 64 bit Windows 7. To make life even more fun, if I build it from the IDE, I get a good binary. If I try to build it using our build script (which calls devenv /batch), I get something that 2012 hates.
Looking at the binaries, it looks like there's a slight difference in code size. using the PE File Explorer. ILSpy thinks that the exes are functionally identical.
Does anybody have a clue what the heck is going on? I have a work around, so I'm not planning on digging further into the binaries, but it's still disconcerting to have the current Windows Server occasionally hating "good" executables.
Mike Swaim