# How to Efficiently Develop and Troubleshoot a Ansible Windows Module

**URL:** <https://forum.ansible.com/t/how-to-efficiently-develop-and-troubleshoot-a-ansible-windows-module/38794>\
**Category:** Ansible Developer\
**Tags:** windows\
**Created:** [May 27, 2024, 9:45am UTC](https://forum.ansible.com/t/how-to-efficiently-develop-and-troubleshoot-a-ansible-windows-module/38794 "2024-05-27T09:45:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yangyang\_Yang](https://avatars.discourse-cdn.com/v4/letter/y/4af34b/32.png) [@Yangyang\_Yang](https://forum.ansible.com/u/Yangyang_Yang)\
**Post date:** [May 27, 2024, 9:45am UTC](https://forum.ansible.com/t/how-to-efficiently-develop-and-troubleshoot-a-ansible-windows-module/38794/1 "2024-05-27T09:45:52Z")

</div>

Hi,

I think it is not uncommon to feel frustrated when developing an ansible module for windows thanks to the pool viability of how ansible windows module is executing on the windows host.

Is there any good way to develop and debug a windows module interactively like one can do with Powershell ISE or Vs Code?

Thanks in advance.