- Home /
- Visual Studio /
Get help from our community supported forum
Report an issue from
within Visual Studio*
This allows diagnostic information to be included in your report
1
Open Visual Studio
2
Select Report a Problem
3
Type and Submit
*Available only on Visual Studio 2017 Preview 3 and newer releases
VS Installer overwrite with old version Azure PowerShell.
install azure powershell $ install-module azurerm
check version $ import-module azurerm $ get-module -Name azurerm ModuleType Version Name ExportedCommands
Script 3.8.0 azurerm {Add-AzureAnalysisServicesAccount, Add-AzureKeyVaultCertificate, Add-AzureKeyVaultCertificateContact, Add-AzureKeyVaultKey...}
install or update VS 2017 with azure development. see attached image
I can not edit this post, so I rewrote it again.
----
1. install azure powershell
$ install-module azurerm
2. check version
$ install-module azurerm
$ import-module azurerm
$ get-module -Name azurerm
ModuleType Version Name ExportedCommands
---------- ------- ---- ----------------
Script 3.8.0 azurerm {Add-AzureAnalysisServicesAccount, Add-AzureKeyVaultCertificate, Add-1.AzureKeyVaultCertificateContact, Add-AzureKeyVaultKey...}
4. install or update VS 2017 with azure development. see attached image png
azure powershell version 2.1.0 installed.
----
This issue is infuriating! The original post is not very clear in my opinion so I will elaborate. Whenever VS 2017 is updated it is installing 'Microsoft Azure PowerShell -September 2016', an outdated version of the AzureRM modules. What is even more infuriating is that if you have installed the latest version of the AzureRM modules from the PowerShell Gallery VS is uninstalling them. I don't know if this only happens for certain VS 2017 install configuration but it is so incredibly frustrating to wake up and discover that all of your scripts are broken because VS has rolled back to outdated modules.
Hello,
I'm taking a look into this issue.
In order for me to investigate , could you please run http://aka.ms/vscollect and attach your %temp%\vslogs.zip . It'll collect the logs I need to dig a little deeper to figure out what might be going on.
Thanks,
-David
Certainly annoying for these of us who have several PS modules all them installed with PS nugget. I don't see that this feature can be manually removed in VS installer without loosing other functionalities.
128 People are following this
