A
Andrew Marshall
Hi there.
I've recently converted our .NET application to VS 2008 and started to have
problems ( a cross thread call exception that was clearly erroneous ) with a
3rd party ActiveX control we use when running on 64bit Vista. After some
research I suspected this was down to DEP and so after consulting Ed
Maurer's blog entry,
http://blogs.msdn.com/ed_maurer/archive/2007/12/14/nxcompat-and-the-c-compiler.aspx
I managed to circumvent the problem by turning off the NXCOMPAT bit in the
binary with a post build event.
As an interim solution for development purposes I am fine with this, but
what are the disadvantages? The application is not particularly security
sensitive so DEP is not of particular interest - but am I likely to run into
compatibility problems in future?
Regards,
Andrew Marshall
Senior Software Engineer
Leica-Microsystems.
I've recently converted our .NET application to VS 2008 and started to have
problems ( a cross thread call exception that was clearly erroneous ) with a
3rd party ActiveX control we use when running on 64bit Vista. After some
research I suspected this was down to DEP and so after consulting Ed
Maurer's blog entry,
http://blogs.msdn.com/ed_maurer/archive/2007/12/14/nxcompat-and-the-c-compiler.aspx
I managed to circumvent the problem by turning off the NXCOMPAT bit in the
binary with a post build event.
As an interim solution for development purposes I am fine with this, but
what are the disadvantages? The application is not particularly security
sensitive so DEP is not of particular interest - but am I likely to run into
compatibility problems in future?
Regards,
Andrew Marshall
Senior Software Engineer
Leica-Microsystems.