Closed nabeelio closed 4 years ago
guperrot
commented
5 years ago Sounds like your own user cannot write to C:\Users\...\AppData\Local\phpVMS\acars.exe_Url_qvl4ekumnzcu5otwp4l1ouhhyqs0jrdk\AppCenter.config which is the user directory.
Does the C:\Users\...\AppData\Local\phpVMS\acars.exe_Url_qvl4ekumnzcu5otwp4l1ouhhyqs0jrdk parent directory exist?
nabeelio
commented
5 years ago It exists, and I deleted the folder and it was recreated on app startup, but still the same permissions error. The permissions on the folder itself are full to my user.
nabeelio
commented
5 years ago And the app.manifest file is just the default:
<?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.app" />
<trustInfo xmlns="urn:schemas-microsoft-com:asm.v2">
<security>
<requestedPrivileges xmlns="urn:schemas-microsoft-com:asm.v3">
~1~ UAC Manifest Options
If you want to change the Windows User Account Control level replace the
requestedExecutionLevel node with one of the following.
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
<requestedExecutionLevel level="requireAdministrator" uiAccess="false" />
<requestedExecutionLevel level="highestAvailable" uiAccess="false" />
Specifying requestedExecutionLevel element will disable file and registry virtualization.
Remove this element if your application requires this virtualization for backwards
compatibility.
@1@
<requestedExecutionLevel level="asInvoker" uiAccess="false" />
</requestedPrivileges>
<applicationRequestMinimum>
<defaultAssemblyRequest permissionSetReference="Custom" />
<PermissionSet class="System.Security.PermissionSet" version="1" ID="Custom" SameSite="site" Unrestricted="true" />
</applicationRequestMinimum>
</security>
</trustInfo>-->
<compatibility xmlns="urn:schemas-microsoft-com:compatibility.v1">
<application>
<!-- A list of the Windows versions that this application has been tested on and is
is designed to work with. Uncomment the appropriate elements and Windows will
automatically selected the most compatible environment. -->
<!-- Windows Vista -->
<!--<supportedOS Id="{e2011457-1546-43c5-a5fe-008deee3d3f0}" />-->
<!-- Windows 7 -->
<!--<supportedOS Id="{35138b9a-5d96-4fbd-8e2d-a2440225f93a}" />-->
<!-- Windows 8 -->
<!--<supportedOS Id="{4a2f28e3-53b9-4441-ba9c-d69d4a4a6e38}" />-->
<!-- Windows 8.1 -->
<!--<supportedOS Id="{1f676c76-80e1-4239-95bb-83d0f6d0da78}" />-->
<!-- Windows 10 -->
<!--<supportedOS Id="{8e0f7a12-bfb3-4fe8-b9a5-48fd50a15a9a}" />-->
</application>
</compatibility>
<!-- Indicates that the application is DPI-aware and will not be automatically scaled by Windows at higher
DPIs. Windows Presentation Foundation (WPF) applications are automatically DPI-aware and do not need
to opt in. Windows Forms applications targeting .NET Framework 4.6 that opt into this setting, should
also set the 'EnableWindowsFormsHighDpiAutoResizing' setting to 'true' in their app.config. -->
<!--
<application xmlns="urn:schemas-microsoft-com:asm.v3">
<windowsSettings>
<dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true</dpiAware>
</windowsSettings>
</application>
-->
<!-- Enable themes for Windows common controls and dialogs (Windows XP and later) -->
<!--
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="*"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
-->
</assembly>```And I have written files to that folder in the past
nabeelio
commented
5 years ago So I removed the app.manifest entirely and it seems to be working now. I'm guessing that's something that would need to be addressed somewhere in the docs or what values I might need to put in there, if I needed to use the manifest file.
guperrot
commented
5 years ago That sounds like a bug we need to fix to be compatible with something in your manifest. Do you mind sharing that file as it was when the issue occurred?
nabeelio
commented
5 years ago Sounds good, thanks. It's the one I posted above.
guperrot
commented
4 years ago I generated the default manifest and it looks like yours. However I don't have any issue with it. I used this method: https://stackoverflow.com/a/55462107/598520 It would be interesting to compare our csproj files if you need to restore the manifest (adding the manifest generates a lot of diff in the csproj file). But since it works with or without the default manifest for us, I don't see anything to document for now.
guperrot
commented
4 years ago Actually my file didn't have sections commented out, but after I replaced with the one you shared to have the same sections commented out, no issue either. I suspect csproj differences instead.
annakocheshkova
commented
4 years ago Hey @nabeelio do you have any updates? If so, please let us know and re-open the issue. Thanks.
Description
Other details are the same as my previous issue #1068
Repro Steps
Please list the steps used to reproduce your issue.
Details
Using the latest prerelease version in a WPF project.
And the verbose logs: