-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup: Cannot install by MSI installer without .NET Framework 3.5 #9402
Comments
Looks like wix customization extension is loading clr 2.0, so we cannot just update our dll to be 4x. Need to create another type of customization (script, exe) to skip wix extension from loading the clr. |
DescriptionRemvoe the customization that detects AzureRM, which should resolve the issue altogether Cost: 1 |
Alternate suggestion: Add a check for .Net 3.5 using either a generic registry search or using the WixNetFxExtension Specifically conditioning a launch condition off of NETFRAMEWORK35 property. |
Do we have an update on this? Is .NET a requirement still? |
Hi @markcowl and @cormacpayne, not sure if this fix was already released but the requirement to enable .Net Framework 3.5 on a Windows 2016 server is still happening. The workaraound I found is to run before installing the MSI: DISM /Online /NoRestart /Enable-Feature /FeatureName:NetFx3ServerFeatures |
Description
Cannot install the Az module by the MSI installer (Az-Cmdlets-2.2.0.28110-x64.msi) without .NET Framework 3.5. The installer ended with the following message.
After install/enable .NET Framework 3.5, the Az module MSI installer works successfully.
At least, this happens on the following OSs (clean install):
Log by
msiexec /i Az-Cmdlets-2.2.0.28110-x64.msi /l*v .\setup.log
:I guess this issue stems from the code below:
https://github.com/Azure/azure-powershell/blob/79a4c8f72b2433c2fe44f330b64442828460284b/setup/InstallerChecks/InstallerChecks/InstallerChecks.config
Steps to reproduce
Environment data
Module versions
Debug output
Error output
The text was updated successfully, but these errors were encountered: