AzureRM commandlets give problems

[JorisK1980]

Product, version and build: PS Studio 2018 1.0.26
Operating system: 2016 64bit

The issue:

When i start a new project, i create a simple form based project. At form_load or button_click, I start loading the AzureRM module which has been installed on the system successfully.

I have a very small script that logs on into Azure successfully, after that, it starts a simple commandlet: Get-AzureRmADApplication -DisplayNameStartWith "XXXXXXXXXXX"

The application hangs, nothing happens.

When i launch it as a script in a seperate/normal powershell window, it works fine.

I can't find any errormessages, the PS Studio log remains silent.

Anyone any idea?

[davidc]

[TOPIC MOVED TO POWERSHELL GUIS FORUM BY MODERATOR]

It could be because the GUI is holding up the pipeline. Try using a job (see: Job Tracker control set) to execute the commands.

https://info.sapien.com/index.php/guis/ ... sive-forms

[mxtrinidad]

It will help if you can provide what version of AzureRm you're currently using.

Thanks!

[JorisK1980]

[TOPIC MOVED TO POWERSHELL GUIS FORUM BY MODERATOR]

It could be because the GUI is holding up the pipeline. Try using a job (see: Job Tracker control set) to execute the commands.

https://info.sapien.com/index.php/guis/ ... sive-forms

There's nothing piped.

All i do is a simple: Get-AzureRmADApplication -DisplayNameStartWith $Name

GUI completely freezes and never comes back.

[jvierra]

Yes. This is an issue with Azure running in a form.

Connect and run one Azure command before opening the form and it should work. It does with Get-AzureADGroup.

[mxtrinidad]

Yes! There are issues running Azure running in Windows Forms. Microsoft has been implementing the '-AsJob' parameter in some of there cmdlets.

So, as mention before, try using the JobTracker form. But, at the same time, I've seen good results using the *-job cmdlets: Start-Job, Get-Job, and Receive-Job.

We are in process of creating some additional templates to tackle the issue with Azure.

[jvierra]

The issue, in al cases that I have tested, has nothing to do with long running commands. The Azure module won'r correctly initialize from inside a form. I think Alex was looking into this with some MS people.

Attached is an example of how to resolve this issue.