-
-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to Configure AppPool as No Managed Code #395
Comments
seems unusual since the documentation is: which should mean that all the tests are using true |
I am planning on looking further into it this weekend. I have a fix for the issue in mind. |
Woops... accidently closed. |
k, if i have time i'll write a specific test for just |
I edited the ticket. The issue only occurs on existing app pools. I apologize for not mentioning this to begin with. |
Thanks for the clarification, currently hitting some deprecation issues then going to look into this |
@idflyfish would this be what you are doing? iis_pool 'test_no_managed_code' do
no_managed_code false
pipeline_mode :Integrated
action [:add, :config, :start]
end then later iis_pool 'test_no_managed_code' do
no_managed_code true
pipeline_mode :Classic
action [:add, :config, :start]
end |
Essentially yes. It works fine when the app pool doesn't already exist. However, once the app pool exists it will not set to no_managed_code. I can verify this both through the UI and via Powershell.
…________________________________
From: Justin Schuhmann <notifications@github.com>
Sent: Thursday, September 21, 2017 12:27 PM
To: chef-cookbooks/iis
Cc: Mike Price; Mention
Subject: Re: [chef-cookbooks/iis] Unable to Configure AppPool as No Managed Code (#395)
@idflyfish<https://github.com/idflyfish> would this be what you are doing?
iis_pool 'test_no_managed_code' do
no_managed_code false
pipeline_mode :Integrated
action [:add, :config, :start]
end
then later
iis_pool 'test_no_managed_code' do
no_managed_code true
pipeline_mode :Classic
action [:add, :config, :start]
end
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#395 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAu4la2ufa-2E28zw5C5F1mf9RitRlMoks5skqp-gaJpZM4PRqh8>.
|
resolved in #403 |
Signed-off-by jmschu02@gmail.com **Description** had to recreate Fixes a bug in iis_pool that causes an issue with resetting to no_managed_code runtime versions **Issues Resolved** #395 **Check List** All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD New functionality includes testing. New functionality has been documented in the README if applicable All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD
Signed-off-by jmschu02@gmail.com **Description** had to recreate Fixes a bug in iis_pool that causes an issue with resetting to no_managed_code runtime versions **Issues Resolved** sous-chefs#395 **Check List** All tests pass. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/TESTING.MD New functionality includes testing. New functionality has been documented in the README if applicable All commits have been signed for the Developer Certificate of Origin. See https://github.com/chef-cookbooks/community_cookbook_documentation/blob/master/CONTRIBUTING.MD
Cookbook version
6.7.2
Chef-client version
12.20.3
Platform Details
Windows Server 2016
Scenario:
Trying to configure the ".NET CLR version" setting on an AppPool to "No Managed Code" for an existing ASP.NET Core application. This is the recommended setting for ASP.NET Core applications since they do not run in a w3wp.exe process.
Steps to Reproduce:
Set the no_managed_code property on a new pool resource to true within a cookbook recipe for an app pool which already exists.
Expected Result:
.NET CLR version set to "No Managed Code"
Actual Result:
.NET CLR Version set to ".NET CLR Version v4.0.30319"
The text was updated successfully, but these errors were encountered: