How to set LARGEADRESSAWARE in no signing assembly projects for a ClickOnce app?

Question

I have an application with the next two Post-Compilation commands:

call editbin /LARGEADDRESSAWARE $(TargetPath)
call editbin /LARGEADDRESSAWARE $(ProjectDir)obj\$(PlatformName)\$(ConfigurationName)\$(TargetFileName)

and works fine.

But when I publish into a server as the ClickOne Application works with no errors but when I try install in a client the hash of file is different than the value calculated in the manifest.

I tryed to use the next command:

sn -Ra $(ProjectDir)obj\$(PlatformName)\$(ConfigurationName)\$(TargetFileName) PublicPrivateKeyFile.snk

but does not work and it shows the next message:

app.exe does not represent any strong-named assembly.

I suppose it's because all my projects has the "signing the assembly" option with false value. Before using LARGEADDRESSAWARE the ClickOnce Application worked fine.

It is necesary to set the "signing the assembly" option with true value for all projects or are there any way to use LARGEADDRESSAWARE with false value for this option?

EDIT:

Solution of Mark Sowul works fine: Also I added in AfterBuild the next lines in order to check if the AfterCompile works fine

call &quot;$(VS110COMNTOOLS)vsvars32.bat&quot;
dumpbin /headers &quot;$(TargetPath)&quot; &gt; &quot;$(TargetPath).info&quot;
findstr &quot;(&gt;2GB)&quot; &quot;$(TargetPath).info&quot;
set BUID_ERRORLEVEL=%ERRORLEVEL%
del &quot;$(TargetPath).info&quot;
if [%BUID_ERRORLEVEL%]==[0] echo EXE program updated to use more than 2GB
if [%BUID_ERRORLEVEL%]==[1] echo ERROR: EXE PROGRAM WAS NOT UPDATED TO USE MORE THAN 2GB
set ERRORLEVEL=%BUID_ERRORLEVEL%

You must be able to sign after setting large address aware. Do you even need to set LAA for a .net project? If so, can't VS do it? — David Heffernan, Oct 30 '13 at 19:32
Yes, I do. I need to set LAA for a .net project and works fine, but in Click Once I don'y know how to do. — Asier Cayón, Oct 30 '13 at 23:24

score 7 · Accepted Answer · answered Mar 24 '14 at 18:12

Post Build events are too late in the game. You have found this out to an extent, as I did, by realizing you need to alter the file in obj.

However, Post Build occurs after the manifest generation. So editing the obj file there is too late. The better place to do it is in the AfterCompile build target.

You'll have to edit the csproj; add after the lines you'll already see for this:

<!-- To modify your build process, add your task inside one of the targets below and uncomment it. 
       Other similar extension points exist, see Microsoft.Common.targets.
  <Target Name="BeforeBuild">
  </Target>
  <Target Name="AfterBuild">
  </Target>
  -->
    **<Target Name="AfterCompile">
        <Exec Command="
call &quot;$(VS110COMNTOOLS)\vsvars32.bat&quot;
editbin /largeaddressaware &quot;$(IntermediateOutputPath)$(TargetFileName)&quot;
" />
    </Target>**

It works fine. I Added my final solution in the first message. Thanks. — Asier Cayón, Mar 25 '14 at 11:20
I had a similar problem when specifying the `NXCOMPAT:NO` flag for editbin. Your solution worked perfectly thanks. — Barrie, Nov 28 '14 at 10:36

How to set LARGEADRESSAWARE in no signing assembly projects for a ClickOnce app?

1 Answers1

Linked