I'm just sayin' - All Comments

re: NXCOMPAT and the C# compiler

Sharad — Mon, 29 Aug 2011 23:15:12 GMT

Is Ed Maurer beiing facetitious when he says they love it so much!!?? Talk of "seemless backward compatiblity"

re: Please allow me to introduce myself

Ed Maurer — Sun, 28 Nov 2010 05:53:05 GMT

I am also responsible for F***ing up the compilers in Microsoft and also screwing employees.

re: NXCOMPAT and the C# compiler

rowter — Tue, 25 Aug 2009 21:45:27 GMT

I got a mappoint failed to load error.

What should i include in the "$(TargetPath")" . What should this be pointing to?

re: NXCOMPAT and the C# compiler

sdasari — Wed, 10 Dec 2008 04:06:33 GMT

I am using VS 2005 and Mappoint Active X control, when i build the application on Vista i am getting the error Mappoint Failed to Load. The i have added the

call "$(DevEnvDir)..\..\VC\bin\vcvars32.bat"

call "$(DevEnvDir)..\..\VC\bin\editbin.exe" /NXCOMPAT:NO "$(TargetPath)"

and executed the application, this time Mappoint is working fine. When i deploy same project with ClickOnce deployment, i am getting Mappoint Failed to load on Vista Desktop. Please suggest me, how can i solve this problem.

re: NXCOMPAT and the C# compiler

ajsllc — Thu, 20 Nov 2008 20:15:26 GMT

I should have added that I am using Visual Studio 2008

re: NXCOMPAT and the C# compiler

ajsllc — Thu, 20 Nov 2008 19:49:24 GMT

I added this to my post-build event on a VB project.

call "$(DevEnvDir)..\..\VC\bin\vcvars32.bat"

call "$(DevEnvDir)..\..\VC\bin\editbin.exe" /NXCOMPAT:NO "$(TargetPath)"

It executes successfully, but if the "primary output" of that project is included in a deployment project, the exe that gets included in the output MSI does NOT have DEP disabled.

I have found that targetpath points to .....\projectname\\bin\x86\Release\projectname.exe

by experimentation, I have also found that if I edit bin ......\projectname\bin\x86\Release\\..\..\..\obj\x86\release\projectname.exe

that is, the obj folder instead of the bin folder

then the exe that gets included in the MSI DOES have DEP disabled.

I'm a happy camper, my problem is resolved, but I am curious as to why.

Is it that the deployment project pulls the output from the wrong folder,

or is it some timing issue about when things are copied from obj to bin?

re: NXCOMPAT and the C# compiler

N!kky — Thu, 16 Oct 2008 19:57:28 GMT

Hi All,

I've got a similar issue. I've got a bug with by COM Interop and by using the following command in my build it get rids of the issue:

call $(DevEnvDir)..\tools\vsvars32.bat

editbin.exe /NXCOMPAT:NO $(TargetPath)

I've got it to work without signing my assemblies with a strong Name. However when we release our software we need to sign our assemblies using a .snk file. I've added the above code to my post build event however i can no longer run my app since it fails with Strong Validation Failed. What i need to do is call the above code and then sign my .exe file. How do i do this through the post build events? I'm currently using the Signing tab in visual studio 9 in my projects properties to sign my assemblies. Is there any other way to do this via the post build event?

Have seen the following command but can not get it to work because i dont know what to put for MyModule.netmodule parameter

al /out:MyAssembly.dll MyModule.netmodule /keyfile:sgKey.snk

Any ideas? Any suggestions will be help. Thanks in advance.

Regards Nik

Disable DEP on applications

Gaurav Bodar's Blog — Tue, 23 Sep 2008 03:05:41 GMT

Windows vista wont Allow ATL control on the machine. We have Data Execution Prevention to stop Executing

re: NXCOMPAT and the C# compiler

rajshreedugar — Fri, 19 Sep 2008 09:26:35 GMT

Hi Awe,

try the following in the post build event command line:-

call "$(DevEnvDir)..\..\VC\bin\vcvars32.bat"

call "$(DevEnvDir)..\..\VC\bin\editbin.exe" /NXCOMPAT:NO "$(TargetPath)"

This works fine for VS2005. You might want to change the location if you are using any other versions of VS. But be sure to include the path within quotes.

Cheers

Rajshree

re: NXCOMPAT and the C# compiler

awe — Tue, 19 Aug 2008 16:01:51 GMT

I tried to run it on my exe, and it worked fine.

Then I tried to include it in the post-build event like you said:

call $(DevEnvDir)..\tools\vsvars32.bat

editbin.exe /NXCOMPAT:NO $(TargetPath)

This gave the following error when I build it:

The command "call C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\..\tools\vsvars32.bat

editbin.exe /NXCOMPAT:NO D:\Work\DotNet\RadiusStudio.NET\RadiusStudio\bin\Release\StudioVision.exe" exited with code 9009.

This is also a problem inside Visual Studio, because it is a GUI control that fails to load in the forms designer. Could this be solved by running EDITBIN.EXE on devenv.exe?