Data Execution Prevention

[TwoSixTwo]

Some of our customers are currently experiencing a problem with Data Execution Prevention on Vista machines. I wanted to post it on this forum to see if anyone else has encountered the problem and how they've solved it. Also, the Kinook folks are pretty helpful. Perhaps they can help, too.

A brief summary: One of our build machines downloaded an update to framework 2.0. It builds several VS2005 projects. I believe the update included a piece that automatically marks executables and/or dll's with activex controls as 'no execute' which then causes an exception from DEP when the control is loaded. (The ActiveX control something from Crystal Reports.)

You can tell DEP that certain programs are excepted, however our executable can't be included in the exceptions list. Here's the message we get on a vista box when we try to add it: This program must run with data execution protection (DEP) enabled. You cannot turn off DEP for this program.

From one patch to the next our program files stopped working for customers.

I believe the problem and a solution is described here.

http://blogs.msdn.com/ed_maurer/arch...-compiler.aspx

Unfortunately the fix described is for C# while we use VB.Net.

I've also tried using the Application Compatibility Toolkit to set the DisableNX bit. I have a database but there's no clear instruction on how that would be deployed.

We can turn off DEP completely, but that's not acceptable.

Any thoughts/solutions would be appreciated.

Thanks,
Dave

PS
I tried emailing Ed Maurer, the blogger linked above, directly but got errors on the page.