Skip to content
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

Failed to install .NET on Vista 32-bit #8

Open
kouk opened this issue Feb 28, 2014 · 3 comments
Open

Failed to install .NET on Vista 32-bit #8

kouk opened this issue Feb 28, 2014 · 3 comments

Comments

@kouk
Copy link

kouk commented Feb 28, 2014

Hello,
At my work we use DotNetChecker to install .NET 4.0, usually on 64 bit Windows (7 and 8). However a client wanted to run it on Vista 32 bit and we tried and found that, while the .NET installer is downloaded, it doesn't even appear to start. This is with user level execution, not admin. I believe the .NET installer wants to get elevated permissions but the ExecWait call in the DotNetChecker script will fail in this case (correct me if I am wrong). One solution I found was using the StdUtils::ExecShellWaitEx macro like this. This works for me. However if there is some better way to solve this or if you want me to contribute this piece of code I would be glad to help.

@bveenvliet
Copy link
Contributor

Is it an option to add the following lines to your base installer?
;Request application privileges for Windows Vista
RequestExecutionLevel admin

@kouk
Copy link
Author

kouk commented Mar 5, 2014

yeah, it's an option but I prefer not to. Our application is installed in %APPDATA% and in most cases the .NET dependency is already available. So no admin privileges are necessary. But as I said, the solution we have works for us. Perhaps the DotNetChecker project would be interested in having StdUtils as an optional dependency for others like us who need user level installs on Vista?

@gwicksted
Copy link

An alternative would be if DotNetChecker.nsh be changed to break up the check/download/install actions into individual macros with the current CheckNetFramework performing all 3 (when required).

Then applications with RequestExecutionLevel admin can continue using the convenient CheckNetFramework macro and those using StdUtils or UAC plugins can implement their own variation of the install portion of the process (which may involve running the .NET installer with a runas verb or re-running the current NSIS installer with elevated privileges).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants