Jump to content

Ruzgfpegk

New Members
  • Posts

    1
  • Joined

  • Last visited

  1. I don't know if I'm misunderstanding something about the .msix format, but it seems to be way easier to "hack" (in the "twist it to our needs" sense, for lack of a better word) than traditional .exe installers. I uncompressed the Affinity Designer 2 .msix file using 7-Zip on a secondary drive, went into the "App" folder and launched Designer.exe as if it was a semi-portable app (by which I mean that the .exe could be anywhere but the profile stays local), registered my trial on it and it worked quite well for basic operations. I didn't test it in depth. Using Sysinternal's handle64 tool I didn't see any files opened elsewhere in the filesystem besides in C:\Users\USER\.affinity\Common\2.0\ and C:\Users\USER\.affinity\Designer\2.0\ . I could also use that Designer.exe as an external editing application from DxO PhotoLab and it received and opened the file correctly. I'm not sure if the issues mentioned by Patrick could be reproduced this way too? If not then this "manual install" could be a workaround in the meantime. In other news, sadly I couldn't run the app in Linux/Wine this way (the old 1.9/1.10 installers just crashed due to some unsupported .NET 4 icon method, now the .exe can't find the DLLs in its own folder), but maybe a winetricks script could be enough now.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.