win_dotnet_ngen - Runs ngen to recompile DLLs after .NET updates
New in version 2.0.
Synopsis
- After .NET framework is installed/updated, Windows will probably want to recompile things to optimise for the host.
- This happens via scheduled task, usually at some inopportune time.
- This module allows you to run this task on your own schedule, so you incur the CPU hit at some more convenient and controlled time.
- http://blogs.msdn.com/b/dotnet/archive/2013/08/06/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up.aspx
Examples
- name: run ngen tasks win_dotnet_ngen:
Return Values
Common return values are documented here Return Values, the following are the fields unique to this module:
name | description | returned | type | sample |
---|---|---|---|---|
dotnet_ngen64_eqi_exit_code | The exit code after running the 64-bit ngen.exe executeQueuedItems command. | 64-bit ngen executable exists | int | 0 |
dotnet_ngen64_eqi_output | The stdout after running the 64-bit ngen.exe executeQueuedItems command. | 64-bit ngen executable exists | str | sample output |
dotnet_ngen64_update_exit_code | The exit code after running the 64-bit ngen.exe update /force command. | 64-bit ngen executable exists | int | 0 |
dotnet_ngen64_update_output | The stdout after running the 64-bit ngen.exe update /force command. | 64-bit ngen executable exists | str | sample output |
dotnet_ngen_eqi_exit_code | The exit code after running the 32-bit ngen.exe executeQueuedItems command. | 32-bit ngen executable exists | int | 0 |
dotnet_ngen_eqi_output | The stdout after running the 32-bit ngen.exe executeQueuedItems command. | 32-bit ngen executable exists | str | sample output |
dotnet_ngen_update_exit_code | The exit code after running the 32-bit ngen.exe update /force command. | 32-bit ngen executable exists | int | 0 |
dotnet_ngen_update_output | The stdout after running the 32-bit ngen.exe update /force command. | 32-bit ngen executable exists | str | sample output |
Notes
Note
- there are in fact two scheduled tasks for ngen but they have no triggers so aren’t a problem
- there’s no way to test if they’ve been completed (?)
- the stdout is quite likely to be several megabytes
Status
This module is flagged as preview which means that it is not guaranteed to have a backwards compatible interface.
For help in developing on modules, should you be so inclined, please read Community Information & Contributing, Testing Ansible and Developing Modules.
© 2012–2018 Michael DeHaan
© 2018–2019 Red Hat, Inc.
Licensed under the GNU General Public License version 3.
https://docs.ansible.com/ansible/2.4/win_dotnet_ngen_module.html