You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the PowerShell extension doesn't fully support PowerShell module files (with .psm1 file extension).
Folding, for example, isn't supported.
It would be a great advantage if the PowerShell extension fully supported .psm1 files, too.
Well, in fact, it would be great to be able to debug these kind of files, too, without being required to always create a .ps1 stub file first (see #133). Suggestion: For debugging a PowerShell file, a dialog might pup up, enabling the user to edit the call to be made within the PowerShell module. The text entered could be used by the extension to create a stub .ps1 file in a temporary directory and run that file. This would keep the user from creating such file manually. The dialog should offer a history, so previous calls could easily be repeated.
The text was updated successfully, but these errors were encountered:
It looks like the PowerShell extension doesn't fully support PowerShell module files (with
.psm1
file extension).Folding, for example, isn't supported.
It would be a great advantage if the PowerShell extension fully supported .psm1 files, too.
Well, in fact, it would be great to be able to debug these kind of files, too, without being required to always create a .ps1 stub file first (see #133). Suggestion: For debugging a PowerShell file, a dialog might pup up, enabling the user to edit the call to be made within the PowerShell module. The text entered could be used by the extension to create a stub .ps1 file in a temporary directory and run that file. This would keep the user from creating such file manually. The dialog should offer a history, so previous calls could easily be repeated.
The text was updated successfully, but these errors were encountered: