4 ms·

For desktop apps. As far a I know, you can't run in IIS native apps.

• mhomde 11y ago
  True, and I'm not sure there would be much point. .Net native is mainly to reduce startup times and reduce memory footprint
• douche 11y ago
  For anything outside massively scaled web applications, I'm not sure IIS is worth bothering with anymore, now that self-hosted OWIN is more stable, and there is a version of ASP.NET MVC that runs on OWIN.
  • guiomie 11y ago
    So, you are saying I could run a .Net Native app in a OWIN ?
    • douche 11y ago
      Apparently I misspoke, and OWIN is not totally compatible with .NET Core yet. Still, I've found that developing and, moreover, deploying, OWIN self-hosted apps is much more pain-free than using IIS. App pool idle timeouts and recycling are a huge pain for anything that utilizes long-term background services, which happens to be the case with most of the stuff I work on. And ensuring that the appropriate IIS role services are installed is much more of a pain for customer deployments than building what you need into an OWIN app.
• e12e 11y ago
  Does anyone happen to know what the AOT cross-platform story is? Can I build executables that targets eg: Linux/x86_64, OS X in addition to Windows 10 (I mean as three separate binaries -- having one monster, multi-target binary might be interesting, but that would be something else...)?