View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003391||3 - Current Dev List||Enhancement||public||2019-07-13 16:45||2019-10-05 10:34|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0003391: consider removing .Net setup from HRD product setup|
|Description||I believe that .Net is installed on all versions of Windows we support. If that's true, then we should remove the .Net setup components from our product setup image.|
Maybe I'm wrong -- if we're still supporting back-level versions of Windows that don't include a version of .Net good enough for our dependency, then maybe we can at least remove .Net from the product setup image and provide a web-based installer.
The .Net setup contributes about 50 megabytes to the size of the downloaded setup image. The .Net setup is required only to support QLM. No other part of the product uses it.
|Additional Information||This blog post has a table showing which versions of Windows include which versions of the .NET runtime by default.|
|Tags||No tags attached.|
|Module||SW License Mgmt|
|Sub-Module||SW License Client|
||3437 (now related) has notes saying that we've encountered a system in the wild without .NET installed. If that diagnosis is accurate, then ti seems like we need to figure out why Setup isn't installing its .NET runtime playload when it's needed. Setup bug? Wrong version? Maybe that diagnosis means this issue is won't fix, and if so, it probably leads to other issues to fix the .NET install failure and to minimize the impact of the .NET runtime on the downloadable file size.|