Guest pkelley Posted February 12, 2009 Posted February 12, 2009 I have a C# .Net application (EXE and DLL) that I want to make Data Execution Prevention (DEP) compliant. What do I need to add to my code to do this? What the application does: The EXE loops around with a list of e-mail user ID's (uids), passing each uid down into the DLL where the DLL makes a SOAP connection to Exchange Web Services (EWS) to retrieve calendar information. In my unit test, I purposely pass down an invalid uid and wait for, and catch, the SOAP/Web Exception. At that point, I get the dreaded, "...Windows has closed this program..." message box, and my EXE is no longer permitted to execute. The uid's that follow, are valid uid's and when permitted to execute (by running the EXE and DLL on Windows XP instead of Windows Vista), continue along perfectly to the end with the requested calendar information. Again, what do I need to do to my C# application (EXE and DLL) to get them to be DEP compliant? NOTE: I'm using Visual Studio 2005 Thank you in advance. Paul Quote
Guest Peter Foldes Posted February 12, 2009 Posted February 12, 2009 Your best bet is to post it over to the following newsgroup On the web: http://www.microsoft.com/communities/newsg...loper.visualc++ do not forget to add ++ -- Peter Please Reply to Newsgroup for the benefit of others Requests for assistance by email can not and will not be acknowledged. "pkelley" <pkelley@discussions.microsoft.com> wrote in message news:B3FED035-4BA8-4CCD-9DFA-5C2C2B4C6584@microsoft.com...<span style="color:blue"> >I have a C# .Net application (EXE and DLL) that I want to make Data Execution > Prevention (DEP) compliant. > > What do I need to add to my code to do this? > > What the application does: > The EXE loops around with a list of e-mail user ID's (uids), passing each > uid down into the DLL where the DLL makes a SOAP connection to Exchange Web > Services (EWS) to retrieve calendar information. > In my unit test, I purposely pass down an invalid uid and wait for, and > catch, the SOAP/Web Exception. At that point, I get the dreaded, "...Windows > has closed this program..." message box, and my EXE is no longer permitted to > execute. > The uid's that follow, are valid uid's and when permitted to execute (by > running the EXE and DLL on Windows XP instead of Windows Vista), continue > along perfectly to the end with the requested calendar information. > > Again, what do I need to do to my C# application (EXE and DLL) to get them > to be DEP compliant? > NOTE: I'm using Visual Studio 2005 > > Thank you in advance. > Paul </span> Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.