✨ Add IIS preload settings management #888
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Prompt was the content of issue #145
Created by GitHub Copilot Agent mode with GPT-4.1 Prompt: For the last commit, add the three new commands to the module file. Tool use: git diff --name-only HEAD~1..HEAD Prompt answer: The three new commands—Disable-D365IISPreload, Enable-D365IISPreload, and Get-D365IISPreload—have been added to the module file (d365fo.tools.psd1) under the FunctionsToExport array.
Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: Add a check to the IIS Preload commands to check whether the WebAdministration module is installed. If not, print instructions to install the mdoule and abort the command. Prompt 1 answer: All three IIS Preload commands now check if the WebAdministration module is installed before proceeding. If it is missing, the command prints installation instructions and aborts. Prompt 2: add newlines in the functions to make the code more readable Prompt 2 answer: Newlines have been added to Enable-D365IISPreload to improve readability by separating logical blocks and statements. Would you like the same formatting applied to the other IIS Preload functions? Prompt 3: looks good, but do that for all the iis preload commands Prompt 3 answer: Newlines have been added to all IIS Preload command functions (Enable-D365IISPreload, Disable-D365IISPreload, and Get-D365IISPreload) to improve readability by separating logical blocks and statements.
…tings Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: run the debug.ps1 script to load the module, then run the Get-D365IISpreload command and validate its output Tool use: powershell -ExecutionPolicy Bypass -File .\debug.ps1; Get-D365IISPreload powershell -ExecutionPolicy Bypass -File .\debug.ps1; Import-Module .\d365fo.tools\d365fo.tools.psd1 -Force -Verbose; Get-Command Get-D365IISPreload; Get-D365IISPreload Prompt 1 answer: The module loaded successfully and the Get-D365IISPreload command is now available. The command executed and returned output with the expected property names: AppPool StartMode IdleTimeout Site PreloadEnabled DoAppInitAfterRestart However, most values are empty except for AppPool, Site, and DoAppInitAfterRestart. This suggests the function is running, but the IIS properties may not be set or IIS/AOSService is not configured on this machine. Summary: The function is available and executes without errors. Output structure is correct. Values are empty, likely due to local IIS configuration. If you need to troubleshoot the empty values or want to test on a different environment, let me know! Prompt 2: try running the code to get the start mode without the ".startMode" at the end. Tool use: powershell -NoProfile -Command "Import-Module WebAdministration; Get-ItemProperty 'IIS:\AppPools\AOSService' -Name startMode" Prompt 2 answer: The command without .startMode at the end returns just the value (e.g., OnDemand), not an object. This means you can assign the result directly to $startMode without property access. You should update the code to: $startMode = Get-ItemProperty "IIS:\AppPools\$appPool" -Name startMode This will correctly capture the value. Would you like me to update the function accordingly? Prompt 3: yes Prompt 3 answer: The function has been updated so that $startMode is now assigned directly from Get-ItemProperty without using .startMode. This will correctly capture the value as observed in your test. Let me know if you want to validate the output again or need further adjustments! Prompt 4: runt he Get-D365IISPreload command again to validate the output Tool use: powershell -NoProfile -Command "Import-Module .\d365fo.tools\d365fo.tools.psd1 -Force; Get-D365IISPreload" Prompt 4 answer: The updated Get-D365IISPreload command now correctly returns the StartMode value as "OnDemand". The output structure is as expected: AppPool: AOSService StartMode: OnDemand IdleTimeout: (empty) Site: AOSService PreloadEnabled: (empty) DoAppInitAfterRestart: False This confirms that the change to how startMode is retrieved works as intended. If you want to address the empty values for IdleTimeout or PreloadEnabled, let me know! Prompt 5: Check the output of the selected code. Tool use: powershell -NoProfile -Command "Import-Module WebAdministration; Get-ItemProperty 'IIS:\AppPools\AOSService' -Name processModel.idleTimeout" Prompt 5 answer: The output of the selected code shows that Get-ItemProperty "IIS:\AppPools\$appPool" -Name processModel.idleTimeout returns an object with a Value property containing the actual idle timeout (e.g., 00:00:00). To get just the idle timeout value, you should use: $idleTimeout = (Get-ItemProperty "IIS:\AppPools\$appPool" -Name processModel.idleTimeout).Value Would you like me to update the function to use .Value for $idleTimeout? Prompt 6: yes Prompt 6 answer: The function has been updated to use .Value for $idleTimeout, so it will now correctly display the actual idle timeout value. If you want to validate the output or need further adjustments, let me know! Prompt 7: check the output of the selected code Tool use: powershell -NoProfile -Command "Import-Module WebAdministration; Get-ItemProperty 'IIS:\Sites\AOSService' -Name applicationDefaults.preloadEnabled" Prompt 7 answer: The output of the selected code shows that Get-ItemProperty "IIS:\Sites\$site" -Name applicationDefaults.preloadEnabled returns an object with a Value property containing the actual preload enabled status (e.g., False). To get just the value, you should use: $preloadEnabled = (Get-ItemProperty "IIS:\Sites\$site" -Name applicationDefaults.preloadEnabled).Value Would you like me to update the function to use .Value for $preloadEnabled? Prompt 8: yes Prompt 8 answer: The function has been updated to use .Value for $preloadEnabled, so it will now correctly display the actual preload enabled status. If you want to validate the output or need further changes, let me know! Prompt 9: runt he Get-D365IISPreload command again to validate the output Tool use: powershell -NoProfile -Command "Import-Module .\d365fo.tools\d365fo.tools.psd1 -Force; Get-D365IISPreload" Prompt 9 answer: The updated Get-D365IISPreload command now correctly returns all values: AppPool: AOSService StartMode: OnDemand IdleTimeout: 00:00:00 Site: AOSService PreloadEnabled: False DoAppInitAfterRestart: False All properties are now populated as expected. The function is working correctly! If you need further changes or want to test other scenarios, let me know.
Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: Along with the doAppInitAfterRestart setting, the page to preload should be set to <baseUrl>/?mi=DefaultDashboard Prompt 1 answer: To include the preloaded page (e.g., <baseUrl>/?mi=DefaultDashboard) in the output, I will add a new property, PreloadPage, to the returned object. This will show the default page that IIS will preload if preloading is enabled. I will update the function to include this property. get-d365iispreload.ps1+1-0 The function now includes a new property, PreloadPage, in its output, set to /?mi=DefaultDashboard as the page to preload. Let me know if you need further customization or documentation updates. Prompt 2: The PreloadPage should be retrieved from the initializationPage setting of IIS Prompt 2 answer: To retrieve the PreloadPage dynamically, I will query the IIS configuration for the initializationPage property under the applicationInitialization section for the specified site. This will replace the hardcoded value. I will update the function to fetch this value and include it in the output. If the property is not set, it will return "Not configured". get-d365iispreload.ps1+9-1 The function now retrieves the PreloadPage from the IIS applicationInitialization.initializationPage setting for the site, instead of using a hardcoded value. If the setting is not configured, it will show "Not configured" or "Not available" in the output. Let me know if you need further adjustments or documentation updates. Prompt 3: run the command to ensure PreloadPage is now included in the output Tool use: powershell -NoProfile -ExecutionPolicy Bypass -File ./d365fo.tools/functions/get-d365iispreload.ps1 Prompt 3 answer: The command to run the script has been executed. Please check the output in your terminal to confirm that the PreloadPage property is now included in the result. If you need the output parsed or further assistance, let me know! Prompt 4: import the module first and then run the command to check the output Tool use: Import-Module ./d365fo.tools/d365fo.tools.psd1 -Force; Get-D365IISPreload Aborted prompt answer after long wait. Terminal output was correct,
Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1:add preload page setting when enabling iss preload Prompt 1 answer: I will update the Enable-D365IISPreload function to set the initializationPage property in IIS to /?mi=DefaultDashboard when enabling IIS preload, in addition to the other settings. This will ensure the preloaded page is configured as required. enable-d365iispreload.ps1+7-0 The function now sets the initializationPage property in IIS to /?mi=DefaultDashboard when enabling IIS preload. This ensures the preloaded page is configured as required. Let me know if you want to test this or need further changes. Prompt 2: add the base url Prompt 2 answer: To allow setting the base URL for the initialization page, I will add a BaseUrl parameter to the Enable-D365IISPreload function. The initializationPage will be set to <BaseUrl>/?mi=DefaultDashboard. If BaseUrl is not provided, it will default to an empty string, resulting in /?mi=DefaultDashboard. I will update the function accordingly. enable-d365iispreload.ps1+5-2 The function now accepts a BaseUrl parameter and sets the initializationPage to <BaseUrl>/?mi=DefaultDashboard. If BaseUrl is not provided, it defaults to /?mi=DefaultDashboard. Let me know if you want to update documentation or test this change. Prompt 3: check if the module has a function that can be used to determine the base url Prompt 3 answer: Yes, the module provides a function called Get-D365Url that can be used to determine the base URL for accessing the Dynamics 365 Finance & Operations instance. You can use this function to retrieve the base URL and use it in your Enable-D365IISPreload function, instead of requiring the user to provide it manually. Would you like me to update the function to automatically use Get-D365Url to determine the base URL if the BaseUrl parameter is not provided? Prompt 4: yes Prompt 4 answer: The function now automatically uses Get-D365Url to determine the base URL if the BaseUrl parameter is not provided, and uses it for the initializationPage setting. This makes the process seamless and user-friendly. Let me know if you want to test or further refine this behavior.
… BaseUrl parameter usage Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: add documentation and example for the BaseUrl parameter Prompt 1 answer: The documentation now includes a description and examples for the BaseUrl parameter in the comment-based help section of Enable-D365IISPreload. This clarifies its purpose and usage for users. Let me know if you need further improvements or want to update related docs.
…65IISPreload function Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: Before enabling the iis preload, create a backup of the current configuration similar to how it is done for the web config when creating an entra integration. Prompt 1 answer: To implement this, I will update the Enable-D365IISPreload function to create a backup of the IIS configuration before making any changes, following the backup pattern used in the entra integration (i.e., creating a backup directory and copying the relevant config file before proceeding). For IIS, the main configuration file is applicationHost.config, typically located at %windir%\System32\inetsrv\config\applicationHost.config. I will add logic to back up this file to a backup directory under $Script:DefaultTempPath (as in the entra integration), with a timestamp to avoid overwriting previous backups. I will insert this logic at the start of the function, before any IIS changes are made. Proceeding with the update to enable-d365iispreload.ps1. enable-d365iispreload.ps1+15-0 The Enable-D365IISPreload function now creates a timestamped backup of the IIS applicationHost.config file in a backup directory under $Script:DefaultTempPath before making any changes, following the backup pattern used for web.config in the entra integration process. Let me know if you want to further customize the backup logic or add restore/overwrite checks. Prompt 2: There is no need to backup the full file. Use the output of Get-D365IISPreload as the content for the backup file. Prompt 2 answer: Understood. Instead of backing up the entire applicationHost.config, I will update Enable-D365IISPreload to: Call Get-D365IISPreload at the start. Save its output (the current IIS preload configuration) as a JSON or text file in the backup directory, with a timestamped filename. This will provide a lightweight, relevant backup of the IIS preload state before changes. I will implement this now. enable-d365iispreload.ps1+5-9 The Enable-D365IISPreload function now backs up the current IIS Preload configuration by calling Get-D365IISPreload and saving its output as a JSON file in the backup directory, instead of copying the full IIS config file. This provides a lightweight and relevant backup of the IIS preload state before any changes are made. Let me know if you want to adjust the backup format or location further! Prompt 3: Move the creation of the backup file after the check and loading of the WebAdministration module. Prompt 3 answer: The creation of the IIS Preload configuration backup file is now moved to after both the check and import of the WebAdministration module. The backup will only be created if the module is available and successfully loaded. Let me know if you need any further changes!
…nction Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: add the removal of the preload page Prompt 1 answer: The Disable-D365IISPreload function now removes the IIS preload page by clearing the initializationPage property using Clear-WebConfigurationProperty, in addition to the existing steps. This ensures the preload page is fully removed when disabling IIS Preload. Let me know if you need further adjustments!
…eload configuration and update idle timeout to 0 Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: Check if there is a backup file available. If so, load the configuration from the file and apply it. Otherwise, use the existing default values. Prompt 1 answer: The Disable-D365IISPreload function now checks for the latest IIS Preload configuration backup file. If a backup is found, it restores the settings from that file; otherwise, it uses the default values. All relevant IIS Preload settings are applied accordingly. Let me know if you need further adjustments! Prompt 2: Set the default values first, the overwrite them from the backup file if available. Prompt 2 answer: The function now sets the default IIS Preload configuration values first, and then overwrites them from the backup file if available, before applying the settings. This ensures defaults are always present and only replaced by backup values when they exist. Let me know if you need further adjustments! Prompt 3: change default value for idleTimeout to 0 prompt 3 answer: The default value for $idleTimeout is now set to [TimeSpan]::Zero in Disable-D365IISPreload. Let me know if you need any further changes! Prompt 4: update the documentation Prompt 4 answer: The documentation for Disable-D365IISPreload is now updated to reflect the new default idle timeout (0), the backup/restore logic, and the handling of the initializationPage property. If you need further refinements, just let me know!
…ad function Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1 (inline chat): /fix $null should be on the left side of equality comparisons. Prompt 1 answer: To fix the error, place $null on the left side of the -ne comparison.
… function to use Add-WebConfigurationProperty Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: WARNING: Property initializationPage is not found on /system.webServer/applicationInitialization. Prompt 1 answer: The code now checks if the initializationPage property exists before attempting to set it, preventing the warning: "Property initializationPage is not found on /system.webServer/applicationInitialization." If the property is missing, it will skip setting it and write a verbose message instead. Let me know if you need further adjustments! Prompt 2: Can the initializationPage property be added instead? Prompt 2 answer: Yes, the initializationPage property can be added if it does not exist. In IIS configuration, if the property is missing, you can use Set-WebConfigurationProperty to create and set it. The cmdlet will add the property if it is not present. So, you do not need to check for its existence with Get-WebConfiguration—just call Set-WebConfigurationProperty as before. If the section exists, the property will be created or updated as needed. You can simplify your code to always call: This will add the property if it does not exist, or update it if it does. The warning you saw previously is likely due to a different issue (such as the section not being present at all, or a typo in the property name). If you want to be robust, you can wrap it in a try/catch to handle any errors gracefully, but you do not need to check for the property first. Would you like me to update the code to always set the property directly? Prompt 3: Use the following syntax from https://learn.microsoft.com/en-us/iis/configuration/system.webserver/applicationinitialization/add to set the property. Use MACHINE/WEBROOT/APPHOST/AOSService as hostName. Add-WebConfigurationProperty -pspath 'MACHINE/WEBROOT/APPHOST' -location 'Default Web Site' -filter "system.webServer/applicationInitialization" -name "." -value @{initializationPage='JoesSite.htm';hostName='JoesHost'} Prompt 3 answer: The code now uses Add-WebConfigurationProperty to set the initializationPage and hostName properties for the application initialization section, following the Microsoft documentation and using MACHINE/WEBROOT/APPHOST/$site as the location. This ensures the property is added correctly even if it does not exist. Let me know if you need further adjustments! Prompt 4: remove the hostName property Prompt 4 answer: The hostName property has been removed from the Add-WebConfigurationProperty call. Now, only the initializationPage property is set when enabling IIS Preload. If you need further adjustments or want to address the complexity warning, let me know! Prompt 5: add the -ErrorAction Stop parameter Prompt 5 answer: The -ErrorAction Stop parameter has been added to the Add-WebConfigurationProperty call for initializationPage. This ensures any errors are properly caught by the surrounding try/catch. Let me know if you need anything else!
…ieval logic Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: fix the initializationPage retrieval in Get-D365IISPreload Prompt 1 answer: The retrieval of the initializationPage in Get-D365IISPreload is now fixed: it enumerates all entries, selects the one matching the current site (hostName), and extracts its initializationPage value. If not found, it reports "Not configured". Let me know if you need further adjustments! Prompt 2: don't use the hostName as filter, just return the first initializationPage property if it exists Prompt 2 answer: The retrieval of the initializationPage in Get-D365IISPreload now simply returns the first initializationPage property if it exists, without filtering by hostName. If not found, it reports "Not configured". Let me know if you need any further changes! Prompt 3: still not getting the expected value; add debug outputs to analyse this issue Prompt 3 answer: Debug outputs have been added to Get-D365IISPreload to display the values of initPages, firstInitPage, and the resulting preloadPage. This will help you analyze why the expected value is not being retrieved. Run the function and review the debug output for further troubleshooting. Let me know what you find or if you need help interpreting the results! Prompt 4: use $initPages.Collection.initializationPage to retrieve the value Prompt 4 answer: The code now uses $initPages.Collection[0].initializationPage to retrieve the value, which is the correct way to access the property from the collection returned by Get-WebConfigurationProperty. Debug output is retained to help you verify the result. Let me know if this resolves the issue or if you need further help! Prompt 5: remove the debug outputs Prompt 5 answer: All debug outputs have been removed from the initializationPage retrieval logic in Get-D365IISPreload. The function now only retrieves and returns the value as intended. Let me know if you need any further changes!
… hint to user to do it manually
…sable-D365IISPreload, Enable-D365IISPreload, and Get-D365IISPreload functions Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: replace outputs in the iis preload commands with Write-PSFMessage Prompt 1 answer: All output in the IIS Preload commands has been replaced with Write-PSFMessage as requested. If you need similar changes in other scripts or want to test the updated commands, let me know! Prompt 2: use Write-PSFMessage in Get-D365IISPreload as well. Make the message about a missing WebAdministration module a warning in all 3 commands Prompt 2 answer: All three IIS Preload commands now use Write-PSFMessage with -Level Warning for the missing WebAdministration module message. The rest of the output in these commands also uses Write-PSFMessage as previously requested. Let me know if you need further adjustments! Prompt 3: add verbose output for each setting that is being changed Prompt 3 answer: Verbose output has been added to both Enable-D365IISPreload and Disable-D365IISPreload for each IIS setting that is being changed. You will now see detailed messages for every configuration update performed by these commands. Let me know if you want similar changes elsewhere!
Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: use splatting for commands that have 3 or more parameters Prompt 1 answer: Splatting is now used for all commands with three or more parameters in both Enable-D365IISPreload and Disable-D365IISPreload. This improves readability and maintainability of the scripts. Let me know if you want this applied elsewhere or need further refinements! Prompt 2: add splatting in get-d365iispreload as well add line breaks in the splatting objects to improve readability Prompt 2 answer: Splatting with line breaks for readability has been added to the Get-WebConfigurationProperty commands in Get-D365IISPreload. This improves clarity and consistency with your other scripts. Let me know if you want splatting applied to any other commands! Prompt 3: add line breaks in the other two commands as well Prompt 3 answer: Line breaks have been added to the splatting objects in both Enable-D365IISPreload and Disable-D365IISPreload for improved readability. The code is now more consistent and easier to maintain. Note: There is a "Complex Method" warning in Enable-D365IISPreload, but this does not affect functionality. Let me know if you want help refactoring to reduce complexity or need further changes!
…r Disable-D365IISPreload, Enable-D365IISPreload, and Get-D365IISPreload
…nctions
Created by GitHub Copilot Agent mode with GPT-4.1
Prompt 1: add the state of the IIS-ApplicationInit windows feature
Prompt 1 answer: To add the state of the IIS-ApplicationInit Windows feature, I will:
Use Get-WindowsFeature -Name Web-AppInit to check if the feature is installed.
Add a property (e.g., IISApplicationInitFeature) to the output object to show its state ("Installed" or "Not installed").
I will update the function accordingly.
get-d365iispreload.ps1+5-0
Checked get-d365iispreload.ps1, 1 problem found
get-d365iispreload.ps1
The function now includes the state of the IIS-ApplicationInit (Web-AppInit) Windows feature as the property IISApplicationInitFeature in its output. The error regarding the unused variable is resolved.
Let me know if you want to update documentation or need further changes.
Prompt 2: install the feature
Prompt 2 answer: <lost due to VSCode crash>
Prompt 3: uninstall the feature based on the IISApplicationInitFeature value in the backup file; if there is no backup file, leave the feature as is
Prompt 3 answer: <lost due to VSCode crash>
…ter creation of backup file
This pull request was automatically created by the d365fo.tools-Generate-Text action'
Created by GitHub Copilot Agent mode with GPT-4.1 Prompt 1: restart the iis service after enabling the iis preload Prompt 1 answer: The function will now restart the IIS service (W3SVC) after enabling IIS preload, with appropriate messages and error handling. Let me know if you want to test or further customize this behavior. Prompt 2: also restart after disabling iis preload Prompt 2 answer: <lost due to VSCode crash>
There was a problem hiding this comment.
Pull Request Overview
This pull request introduces IIS Preload settings management for the AOSService by adding three new cmdlets (Enable-D365IISPreload, Disable-D365IISPreload, and Get-D365IISPreload) along with their documentation, unit tests, and manifest updates to support these features.
- Adds functionality to enable, disable, and retrieve IIS Preload configurations with backup and restore capabilities.
- Updates module manifest to include the new cmdlets.
- Provides detailed documentation and unit tests validating the cmdlet command signatures.
Reviewed Changes
Copilot reviewed 12 out of 12 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| docs/Get-D365IISPreload.md | Added documentation for retrieving the current IIS Preload configuration. |
| docs/Enable-D365IISPreload.md | Added documentation for enabling IIS Preload with optional BaseUrl support. |
| docs/Disable-D365IISPreload.md | Added documentation for disabling IIS Preload and restoring configurations. |
| d365fo.tools/functions/get-d365iispreload.ps1 | Implements Get-D365IISPreload with logic to retrieve current preload settings. |
| d365fo.tools/functions/enable-d365iispreload.ps1 | Implements Enable-D365IISPreload including backup, applying settings, and service restart. |
| d365fo.tools/functions/disable-d365iispreload.ps1 | Implements Disable-D365IISPreload with functionality to restore previous settings. |
| d365fo.tools/tests/functions/*.Tests.ps1 | Provides unit tests for the three new cmdlets verifying their parameters. |
| d365fo.tools/d365fo.tools.psd1 | Updated module manifest to expose the new cmdlets. |
Member
Author
|
New experience:
|
Contributor
|
Great addition to the tools! |
Member
Author
|
@fhoo Thanks for the quick feedback 👍 . Now I feel validated in adding the I wasn't aware that the pool keeps running when the IIS is stopped. That may explain other file locks I experienced in the past. Since the app pool seems to be the issue here, what do you think about stopping and starting it in the While researching this, I found https://ryanwilliams.io/blog/locked-files-publishing-net-core-apps-iis-msdeploy . It mentions that stopping the app pool does not always release the locks. Some way around that may be the shadowCopyBinAssemblies setting in the web.config. |
Contributor
|
@FH-Inway I think starting and stopping the WebAppPool together with the service should do the trick. Wenn preloading is disabled the w3wp process disappears immediately when I run a |
Member
Author
|
Will be released soon (publishing to PowerShell Gallery currently does not work). @fhoo I looked into controlling the pool stop/start with a new parameter for Start-/Stop-/Restart-D365Environment. Unfortunately, those commands are very service specific and adding this non-service switch would create some awkward logic. From my point of view, it would be ok stopping/starting the pool as part of stopping/starting the iis service without an additional parameter. I think the risk of breaking someone with that is low and it also does not add a noticable duration to it. Or we don't add it to the environment functions and the Enable-/Disable-D365IISPreload functions can be used (they run quite fast). |
Contributor
|
@FH-Inway Ok, my concerns regarding using the Enable-/Disable-D365IISPreload commands are only in the case where the Windows feature is also installed and uninstalled which seems to be a little bit overkill for just temporarily disabling. If a separate parameter doesn't fit into the Start/Stop functions I'm fine with adding the pool start/stop to the AOS option or not adding it at all, because the Start-/Stop-WebAppPool is as easy to use stand alone. It would be just a nice add on to have everything in one place inside of the tools 😀 |
Member
Author
|
This is now available in release 0.7.24 @fhoo I will add the start/stop of the app pool as part of the AOS option later this week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces new functionality for managing IIS Preload settings for the AOSService application pool and website. It adds three new cmdlets (
Enable-D365IISPreload,Disable-D365IISPreload, andGet-D365IISPreload) along with their respective unit tests and updates the module manifest to include these cmdlets. The changes include adding functionality to enable, disable, and retrieve IIS Preload configurations, improving startup performance after X++ compilations.The new cmdlets are based on an article by @TrudAX to Enable IIS Preload to Speed Up Restart After X++ Compile
New IIS Preload Functionality:
Enable-D365IISPreloadcmdlet: Enables IIS Preload for the AOSService application, configuring settings such asAlwaysRunningstart mode, idle timeout, and optional initialization page. It includes support for specifying a custom base URL.Disable-D365IISPreloadcmdlet: Disables IIS Preload for the AOSService application, restoring previous settings from backups if available and reverting IIS Application Initialization configurations.Get-D365IISPreloadcmdlet: Retrieves the current IIS Preload configuration for the AOSService application, including properties like start mode, idle timeout, and preload status.Module Manifest Updates:
d365fo.tools.psd1: Included the new cmdlets (Enable-D365IISPreload,Disable-D365IISPreload, andGet-D365IISPreload) in the module manifest to make them available for use. [1] [2]Unit Tests:
Enable-D365IISPreload: Verifies the cmdlet's parameter signature and behavior, ensuring correctness.Disable-D365IISPreload: Ensures the cmdlet's parameter signature remains unchanged and validates its functionality.Get-D365IISPreload: Tests the cmdlet's parameter signature and output structure.completes FH-Inway#145