-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
cross build win-x64 on macOS: app.manifest requireAdministrator not working #91047
Comments
Tagging subscribers to this area: @vitek-karas, @agocke, @VSadov Issue DetailsDescriptioncross build win-x64 on macOS: app.manifest requireAdministrator not working Reproduction StepsOn macOS:
<?xml version="1.0" encoding="utf-8"?>
<assembly manifestVersion="1.0" xmlns="urn:schemas-microsoft-com:asm.v1">
<assemblyIdentity version="1.0.0.0" name="MyApplication"/>
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
</requestedPrivileges>
</security>
</trustInfo>
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
</application>
</compatibility>
</assembly>
Expected behaviorrequireAdministrator works Actual behaviorthe requireAdministrator setting is not working: Regression?No response Known WorkaroundsNo response ConfigurationNo response Other informationNo response
|
It's a known issue: #66906 |
This is #3828. It has been fixed in .NET 8 - you should be able to use the .NET 8 SDK to target net7.0 and the fix should still apply. |
Thanks |
Description
cross build win-x64 on macOS: app.manifest requireAdministrator not working
Reproduction Steps
On macOS:
dotnet new console
(dotnet 7)<ApplicationManifest>app.manifest</ApplicationManifest>
to csprojdotnet build -r win-x64 --no-self-contained
Expected behavior
requireAdministrator works
Actual behavior
the requireAdministrator setting is not working:
Regression?
No response
Known Workarounds
No response
Configuration
No response
Other information
No response
The text was updated successfully, but these errors were encountered: