-
Notifications
You must be signed in to change notification settings - Fork 182
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
BuildMsi() Requires elevated privileges #1749
Comments
Hello |
I didn't try to run as admin directly. |
This means that when your build script (setup.cs) fails it prints the error messages in the build output some dotnet.exe/msbuild.exe can interpret the errors and fail the entire build. If you want to detect the failure in the build script itself then you need to check the return value of |
It is returning null always. And when I check the folder, the msi file is not created. |
It cannot be always since you wrote this "Then I tried to run it with elevated privileges and it was creating a msi file as well as returning the path of the file." So for some reason in that environment, you need to be elevated. You can also debug the project by yourself. Just disable 'just my code', put breakpoint at BuildMsi and go in with F11 when the breakpoint fires. |
I'm using the BuildMsi() method of WixSharp.Compiler in my Web Application. I have hosted it in IIS and when I run the Application Pool in Local System account (Highest Privilege), the method creates a msi file and returns the path of the file. Whenever I run it un ApplicationPoolIdentity, msi file isn't created and null is returned.
Need help in overcoming this issue.
The text was updated successfully, but these errors were encountered: