{"id":4197,"date":"2017-12-30T17:20:00","date_gmt":"2017-12-31T01:20:00","guid":{"rendered":"https:\/\/www.coretechnologies.com\/blog\/?p=4197"},"modified":"2022-05-01T22:39:27","modified_gmt":"2022-05-02T05:39:27","slug":"force-dot-net-64-bit","status":"publish","type":"post","link":"https:\/\/www.coretechnologies.com\/blog\/alwaysup\/force-dot-net-64-bit\/","title":{"rendered":"Q & A: How do I force my .NET console application to run 64-bit?"},"content":{"rendered":"
\"Q<\/div>\n
\n  We have installed AlwaysUp version 9.7.2.88 (Sep. 2 2016) on Windows Server 2012 R2 Standard. We have multiple jobs that run a 64-bit .NET Console Application as a windows service, but we keep getting a SystemOutMemoryException error. What we found watching the Task Manager is that the EXE always runs as 32-bit. How do we get AlwaysUp to run the console app as 64-bit<\/b>?<\/p>\n

— Clayton<\/p>\n<\/div>\n

\nHi Clayton. There are a couple of ways to force your .NET application to run in 64-bit mode:\n<\/p>\n

    \n
  1. \n

    Build a 64-Bit .NET Version<\/b><\/h2>\n

    \nIf you use Microsoft’s Visual Studio<\/a>, the build configuration is likely be set to Any CPU<\/b> (the default):
    \n
    \n\"Visual<\/a>\n<\/p>\n

    \nThis will produce an executable that will run in either 32-bit or 64-bit mode, depending on the version of .NET available.\n<\/p>\n

    \nTo run your executable in 64-bit only, change the configuration to x64<\/b> and rebuild.\n<\/p>\n

    \nIf your project doesn’t have a x64 configuration, create one like this:\n<\/p>\n

      \n
    1. \n

      Select Build > Configuration Manager…<\/b><\/p>\n<\/li>\n

    2. \n

      In the Configuration Manager, <\/p>\n<\/li>\n

    3. \n

      click the Active solution platform<\/b> entry and select <New><\/b> from the menu that appears:
      \n
      \n\"Create<\/a>\n<\/p>\n<\/li>\n

    4. \n

      In the New Solution Platform<\/b> window, choose x64<\/b> in the top box. We recommend copying settings from Any CPU<\/b> and creating new project platforms (the default):
      \n
      \n\"Create<\/a>\n<\/p>\n<\/li>\n

    5. \n

      Click the OK<\/b> button to record your changes. Close the Configuration Manager<\/p>\n<\/li>\n

    6. \n

      You should now have x64 as a build option. Set it and recompile to produce a 64-bit only executable:
      \n
      \n\"Activate<\/a>\n<\/p>\n<\/li>\n<\/ol>\n

    7. \n

      Use CorFlags to Force .NET 64-Bit<\/b><\/h2>\n

      \nIf your application is built with “Any CPU” but you can’t rebuild it in Visual Studio, Microsoft’s free CorFlags utility<\/a> will come to the rescue.\n<\/p>\n

      \nCorflags.exe is distributed with the Windows 10 SDK<\/a>. Be sure to select the “.NET Development Tools” component when installing.\n<\/p>\n

      \nWe actually found the CorFlags exe file in a couple of places on our hard drive:<\/p>\n

      C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v10.0A\\bin\\NETFX 4.6.1 Tools\\Corflags.exe<\/p><\/blockquote>\n

      C:\\Program Files (x86)\\Microsoft SDKs\\Windows\\v7.0A\\Bin\\Corflags.exe<\/p><\/blockquote>\n

      \nYou may find CorFlags in older .NET SDK installations as well — it has been around since the release of .NET 2.0 (2005).\n<\/p>\n

      \nOnce you have located CorFlags:\n<\/p>\n

        \n
      1. \n

        Make a copy of the executable you want to run in 64-bit. The application we used for testing is called SystemInfoDotNet.exe, so we copied it to SystemInfoDotNet64.exe.<\/p>\n<\/li>\n

      2. \n

        Open a command prompt with admin rights.<\/p>\n<\/li>\n

      3. \n

        CD to the folder containing the copied application.<\/p>\n<\/li>\n

      4. \n

        Run CorFlags on the copied application file. Specify the \/32BIT-<\/b> option to strip away the ability to run in 32-bit mode:
        \n
        \n\"Run<\/a>\n<\/p>\n<\/li>\n<\/ol>\n

        The copied executable will always run in 64-bit mode.<\/p>\n

        For example, our SystemInfoDotNet utility — which displays basic process and system information — normally runs in 32-bit mode:
        \n
        \n\"SystemInfoDotNet<\/a>\n<\/p>\n

        But after running CorFlags on SystemInfoDotNet64, it magically runs in 64-bit mode:
        \n
        \n\"SystemInfoDotNet<\/a>\n<\/p>\n<\/li>\n<\/ol>\n

        <\/p>\n

        \nBest of luck with your .NET application Clayton!<\/p>\n