Mark Ingram
-
Posts
5,358 -
Joined
-
Last visited
Posts posted by Mark Ingram
-
-
Pros:
- MSI had an installation success rate of ~85% (and we have many requests to our tech support team for v1 install failures). MSIX promises a 99.9% success rate.
- MSI requires admin privileges to install. MSIX installs per-user, but files are deduplicated so that disk space isn't wasted.
- MSI apps are not sandboxed from other applications, meaning other applications can break those apps (we have seen this with several third-party apps in the past). MSIX apps are sandboxed to prevent this.
- MSI updates require a manual download of the full ~550mb installer which must be manually installed. MSIX can perform in-app delta updates which are smaller and faster.
- MSI updates can only be performed one at a time. MSIX can update all three apps simultaneously.
- MSI cannot guarantee that an uninstall will leave your machine in the exact state prior to install. MSIX installs are segregated and don't rely on the registry or special filesystem locations meaning an uninstall always leaves you in a clean state. Installation and app data paths are cleaned on uninstall.
- MSI apps cannot integrate with Microsoft Photos app to provide "Edit In..." style features. MSIX can.
- MSI does not require a digital signature. MSIX does (this means any MSIX that appears to be from Serif, will be guaranteed to be from us and only us).
Cons:
-
MSI can allow the user to change the installation directory. MSIX can move installed apps to different drives, but it cannot choose a specific directory (due to the sandbox). See below:
-
MSI can allow an option to install a desktop shortcut. MSIX doesn't provide this as an option, but you can pin the apps to either the Start Menu or the Taskbar. There is also the secret Shell:AppsFolder location in Explorer that allows you to right-click or drag the icon to your Desktop for a shortcut as a workaround if you need it.
-
MSI has easy discovery of undocumented app locations for launching from a third-party. MSIX hides the install location due to the sandbox, but we use App Execution Alias to enable this scenario. You can find the aliases in the following location:
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias , and the next post includes aflaunch.exe as a work around if you need that instead.
- Uncertified, Mr. Doodlezz, nucleardirk and 44 others
-
18
-
13
-
3
-
2
-
11
-
56 minutes ago, xramonx said:
I don't like the way V2 installs. Do not understand why I can no longer choose the installation directory itself.
I do not install programs on "C" (Win).
Should be urgently changed again!!!
I don't understand the sense! Worked fine with the V1 too.You can change the drive after the app has been installed by going to Installed apps in Windows' Settings:
-
2 minutes ago, Truth42 said:
I just did but they seem to have disappeared from this forum. Another try:
Thanks @Truth42. Which app did you buy the Universal Licence in? If you bought the Universal Licence in Affinity Photo for example, you need to register that licence against an Affinity ID in that app. That will allow you to then run the other apps.
-
48 minutes ago, N.P.M. said:
Perhaps an aflaunch for pub and designer are also in order.
Just for the ease of mind for people trying to rightclick to open downloads or files in explorer or dam.It's mentioned in my link, but you can use -a Publisher2 to launch Publisher. Though I know some DAM apps don't let you specify additional arguments, so I will look at dedicated launcher apps for each.
-
As this thread was created in 2019, I'm going to lock it to avoid confusing v1 and v2 answers.
-
On 11/11/2022 at 8:51 PM, Michael Lucero said:
lphilpot, I cut and pasted your path into On1's field. Even though the file was copied as a psd for use with Photo, I got a window that says I may have a permission issue. Any idea how to set the permissions correctly?
Michael
We use App Execution Alias to enable this scenario. You can find the aliases in the following location:
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Remembering to replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can often launch them without even specifying the full path, e.g. just AffinityPhoto2.exe. There are bugs in some third-party applications with the App Execution Alias so I'm working on an aflaunch app that will bridge the gap here.
-
7 minutes ago, Truth42 said:
Doesn't work for me either. Have requested a refund from Apple but they are refusing to do so
Could you provide any screenshots of the problems so we can help out? Are you getting error messages? Were you prompted to register your licence with your Affinity ID after purchasing your licence?
-
On 11/12/2022 at 10:01 AM, Patrick Bell said:
Clearly a bug in Affinity Photo since what worked before fails now because of the new way that Photo gets installed.
It's a bug in Lightroom failing to launch our application, however, I've written an aflaunch app which can work around the problem. Please see here:
-
Thanks for the update @CliveH. For anyone wondering what he's referring to:
-
On 11/10/2022 at 7:09 PM, Danielx64 said:
Hi Lee
What happened is that I downloaded and installed all 3 apps and when I start each app I get a screen like the one in my starting post with no option to start a trial.
Cheers
Login with your Affinity ID, then you'll be given an option to start a trial.
-
2 minutes ago, mb6391 said:
Thanks Mark although I'm sure most posters/readers of this forum will be aware of the install path(s) by now. From memory there is or was not any mention of this during the actual install process. So many users who do not visit these parts will be left in the dark and no doubt possibly highly frustrated.
Anyway, V2 is what it is and it is of course entirely an individual choice whether to live with it or revert back to V1 as I have done.
I think that's a good point. We haven't done a good job of explaining this either in-app or via our help. I'll see that we improve that.
-
7 hours ago, rvst said:
There is an easy way Affinity could fix this problem while still keeping the Windows App architecture.
Install as a Windows App, but then create stub executables that contain only the relevant icon in C:\Program Files\Affinity\Photo\Photo.exe. This stub executable will simply exec the real executable located in C:\Program Files\WindowsApps\<mangled name>\App\Photo.exe. The installation can also create a normal program group in the start menu as well as desktop links, at the option of the user.
I've mentioned elsewhere that we use "App Execution Alias" to enable this scenario. You can find the aliases in the following location:
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Please replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can launch them without even specifying the full path, e.g. AffinityPhoto2.exe.
-
7 hours ago, rvst said:
I recommend the following fix that you implement ASAP in a maintenance release: when installing, create a stub executable in C:\Program Files\Affinity\Photo that contains a copy of the icon and invokes the executable stored in C:\Program Files\WindowsApps\<mangled installation folder name>\App\Photo.exe. Rinse-repeat for Designer and Publisher. In this way, the applications will be accessible using the standard desktop interface metaphor of Windows as well, instead of only via their ridiculous Windows App model that nobody I know even uses.
I've mentioned elsewhere that we use "App Execution Alias" to enable this scenario. You can find the aliases in the following location:
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Please replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can launch them without even specifying the full path, e.g. AffinityPhoto2.exe.
-
25 minutes ago, CliveH said:
Sorry but just tried this and unless I'm doing something wrong it doesn't work with Lightroom 6.14 (last perpetual version - I'm still hanging onto that hoping for an Affinity DAM).
Like theDakota it launches Photo2 but then just gives a series of failed messages. The only thing I've found to work is Walt's BAT file.
Clive
I imagine you might have spaces in your path? I’ll see if I can fix that…
-
9 minutes ago, myclay said:
how would that aflaunch.exe be used when there is no way to add those arguments in the other program?
I've updated the binary to default to Photo now. Please try the new version.
-
For anyone that would like to work around issues with launching our apps from third-party applications (e.g. DxO, ACDSee, etc), I have written a launcher utility that you can place anywhere on your system, and it will take care of calling our apps, with any required arguments.
Usage: aflaunch -a name -b build [args] -a name : One of the following Designer2 Photo2 [Default] Publisher2 -b build : One of the following Retail [Default] Beta MSStore args : [Optional] All remaining arguments to be passed onto the target application (must be last)The -a and -b arguments are optional, so you can ignore them unless you want to launch a different app, or the beta or MS Store versions.
I have signed the exe as well, so it will have a valid digital signature.
Please let me know how you get on with this.
Updated: 12/11/2022 @ 11:04am UTC. Now deals with spaces in filenames.
-
The minimum requirement for Windows is Windows 10 May 2020 Update.
-
8 minutes ago, thedakota said:
That exactly matches what I was already doing. I get an error message that prevents either DxO or ACDSee opening Affinity.
I appreciate that this answer won't help you right now, but the bug is within DxO and ACDSee. If you try something like the following on the command line:
C:\Users\my_username>AffinityPhoto2.exe Downloads\IMG_9849.jpg
Or,
C:\Users\my_username>C:\Users\my_username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe Downloads\IMG_9849.jpg
Then Photo will correctly load the specified image.
-
3 minutes ago, Balveda said:
Just tried this @thedakota it worked for me, C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe as you see removing the < and > around username is key to this. Thanks very much for posting this as it's a far neater solution than messing about with security settings. Cheers.
Thanks for that feedback @Balveda. I hadn't considered that the < and > could cause confusion, so I'll edit my original posts to remove them and clarify that username should match your Windows username.
-
I've mentioned elsewhere that we use "App Execution Alias" to enable this scenario. You can find the aliases in the following location:
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityDesigner2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPhoto2.exe
C:\Users\username\AppData\Local\Microsoft\WindowsApps\AffinityPublisher2.exe
Please replace username with your Windows username. Also, those paths are already in your %PATH% variable so you can launch them without even specifying the full path, e.g. AffinityPhoto2.exe.
-
31 minutes ago, trekki said:
Why can't I install V2 like V1 ?
I do not want to install everything on the C diskYou can move the installation to another drive via (Windows) Settings. Go to Apps > Installed Apps, and find the Affinity app you've installed, click the "..." and choose "Move". e.g.
-
16 minutes ago, Rallyz said:
Another vote for a standard installer. I can't install .msix on Windows 8.1 (yes, I know ...).
Hoping this will be sorted soon, otherwise I'll have to ask for a refund before the 14 days is up.
The installer isn’t the problem here - unfortunately we don’t support Windows 8.1 (the minimum we support is Windows 10 May 2020 update). If you can’t update your OS I suggest you seek a refund. Sorry.
-
11 minutes ago, myclay said:
3DCoat
3dcoat.comBut I can confirm that those install aliases work with Blenders Image Editor linking. (Edit Externally as well as "Screen Grab" Feature with quick Edit and Apply.
Sounds like a bug report needs filing with the developers of 3DCoat. I’m happy to assist if they need any help or info.
-
11 minutes ago, JimInFlorida said:
That's what I get after the installs, same for Photo, Designer and publisher
Sorry if I’m missing something here, but what “installs”? Is this an error from another app?
Extremely disappointed that this installs as an "App" and not regular software program
in Pre-V2 Archive of Affinity on Desktop Questions (macOS and Windows)
Posted
This is a common statistic from Microsoft across all MSI installations. This is just one of many reasons why Microsoft want application developers to migrate to MSIX.