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
Add Comment
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.
Please stop using the MSI Version in the installer and use the PSGallery Version instead. It doesn't require downloading the entire MSI when updates ony affect individual modules.In order to keep Windows 7 Installs supported Install either WMF5.1 or the PowerShellGet Module.PSGallery is the Microsoft recommended way of installing Azure PowerShell.https://docs.microsoft.com/en-us/powershell/azure/install-azurerm-ps
Thank you for your feedback. We have determined that this actually a suggestion not an issue. Please feel free to log suggestions for us at https://visualstudio.uservoice.com . Thank you for helping us build a better Visual Studio.
Solution by
Add Comment
This solution works, but it shouldn't be necessary. If Visual Studio looks for updates and alerts to download them, then the Visual Studio Installer should be going out to this repo, prompting that an updated release is available, and process the update through the Visual Studio Installer. More preferable, Visual Studio should integrate with PowerShell PackageManager, so that they're all able to be managed without one superseding the other. VS2017's OS requirements for Windows are only for Windows operating systems that are compatible with WMF 5.x, so I don't see an issue with making WMF 5.x and the PowerShell PackageManager a requirement for PowerShell dependent workloads
Solution by
Add Comment
@MICROSHAFT: So here is yet another example of proof that you clearly DO NOT listen or give a damn about what your customers want / think. I've just discovered VS has removed the latest Azure PS modules AGAIN, replacing them with your MSI version that is now a YEAR old. How in God's name is this an update? Does time go backwards for you (actually, it would explain a lot)?
How many votes will it take for you to FIX IT!!!!!!!!! Perhaps I should start charging you for the wasted hours this causes. Maybe when it affects your pocket, you'll listen.
