BUG: Application Pool not getting set to "No Managed Code"

[mrhoades]

When I tell Advanced Installer to create a new Application Pool under the IIS section, then I set the .NET Framework version to "No managed code" (for the new ASP.NET core), it creates the application pool, but it sets the .NET version in IIS to .NET 4.x instead of "No managed code" as specified in the configuration settings.

[Daniel]

Hello,

First of all please accept my apologies for the delayed reply.

Indeed, this is an Advanced Installer issue. Thank you for bringing this to our attention. A fix will be available in the future. We will notify you as soon as the fix will be out.

Until then as a workaround you can use our "IIS Custom Properties" support to set the .NET CLR version. You should just set the "ApplicationPool-> managedRuntimeVersion" attribute to "No Managed Code". Here are the steps to proceed with:
1. in "IIS" page select your app pool item and go to "Basic Pool Settings" tab
2. set the ".NET Framework version" to "<default>"
3. go to "Custom Properties" tab and add a new attribute like this:

• Section: <ApplicationPool>
  Name: managedRuntimeVersion
  Type: string
  Value: No Managed Code

4. rebuild and test again the project

All the best,
Daniel

[mrhoades]

Thanks for your help!

[Daniel]

You're always welcome.

All the best,
Daniel

[louisSchnetler]

Has this been fixed? I'm still getting the same error on 13.8.1

[Daniel]

Hello and welcome to our forums,

I'm afraid this issue still has a pending status. We will update this thread as soon as a fix will be released.

Thank you for your understanding.

All the best,
Daniel

[bakkelim]

Hi,

The workaround does not work for me. Instead of selecting "No Managed Code", a new option is created. Also the app pool crashes and stops when trying to access the website.
When manually selecting the first "No Managed Code", the website works as normal.

I am running IIS on a Windows 2012 R2 server.

app pool.png (11.04 KiB) Viewed 12457 times

Regards,
Marius

[Daniel]

Hello Marius and welcome to our forums,

Indeed it seems the previous workaround I offered it just adds a bogus entry set for the "managedRuntimeVersion" flag. I didn't catch this when I previously tested the workaround.

Anther workaround you can try would be to launch the appcmd tool to set the "managedRuntimeVersion" flag. Here are the steps to proceed with:

1. go to "Custom Actions" page and add a new "launch file" custom action with sequence
2. schedule the custom action to run after "Install Execution Stage -> Finish Execution" action group
3. configure the custom action like this:

• File to launch: [SystemFolder]inetsrv\appcmd
  Command Line: set apppool /apppool.name: "MyAppPoolName" /managedRuntimeVersion:""

4. rebuild and test the package

Let me know if this worked.

All the best,
Daniel

[bakkelim]

Hi Daniel,

Your solution worked!
Thanks a lot

Best Regards
Marius

[Daniel]

You're always welcome Marius.

All the best,
Daniel

[Dan]

Hello,

This was fixed in version 14.1 of Advanced Installer released on June 30th, 2017.

Best regards,
Dan

[bakkelim]

I can confirm that this is now working.

Regards,
Marius

[Daniel]

Thank you for your follow up Marius.

All the best,
Daniel