Affinity Photo ,exe File not Easily Available

[Jestertheclown]

Obviously, we all know that. It's what the whole thread is about.

If it did, there would be no need for all this messing about.

Not much point in posting that quote then.

Not everyone is as unhelpful as you.

And posting a quote which was completely erroneous was helpful . . . ?

In what way was it erroneous?

Re-read my earlier post.

The one to which you responded with the above.


"It's good to be . . . . . . . . . Me!"

 

[Digital Nigel]

Obviously, we all know that. It's what the whole thread is about.

If it did, there would be no need for all this messing about.

Not much point in posting that quote then.

Not everyone is as unhelpful as you.

And posting a quote which was completely erroneous was helpful . . . ?

In what way was it erroneous?

Re-read my earlier post.

The one to which you responded with the above.

I provided a fix that works perfectly with PhotoLab and FastStone exporting to AP2. I implemented it in both in no time at all, and now have no trouble sending images to AP2. Other people have done it with several other programs.

So why do you think it's completely erroneous to suggest that the same simple fix would probably work with PR2?

Methinks you don't know what you're talking about.

 

[jfriend00]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

 

[Jestertheclown]

I provided a fix that works perfectly with PhotoLab and FastStone exporting to AP2. I implemented it in both in no time at all, and now have no trouble sending images to AP2. Other people have done it with several other programs.

So why do you think it's completely erroneous to suggest that the same simple fix would probably work with PR2?

Methinks you don't know what you're talking about.

All of which has nothing to do with the quote that you posted:

"Next, in the Applications folder (Mac) or the Programs folder (PC), select the desired program, and click Open."

You'd be wasting your time looking for Affinity Photos 2 in the programmes folder because it isn't there.

That's what this thread's about.

You even responded with some smart remark that you 'obviously' knew that.


"It's good to be . . . . . . . . . Me!"

 

[Digital Nigel]

I provided a fix that works perfectly with PhotoLab and FastStone exporting to AP2. I implemented it in both in no time at all, and now have no trouble sending images to AP2. Other people have done it with several other programs.

So why do you think it's completely erroneous to suggest that the same simple fix would probably work with PR2?

Methinks you don't know what you're talking about.

All of which has nothing to do with the quote that you posted:

"Next, in the Applications folder (Mac) or the Programs folder (PC), select the desired program, and click Open."

You'd be wasting your time looking for Affinity Photos 2 in the programmes folder because it isn't there.

Oh dear, now you're really proving you haven't a clue what you're talking about. Not that there was any doubt.

That's what this thread's about.

You even responded with some smart remark that you 'obviously' knew that.

Well, obviously I did, because I located (on another forum, not my own invention) and implemented the simple workaround. The same workaround would almost certainly work with PR2. And it would take less time to set up than you've taken proving you're clueless.

"It's not good to be ignorant and stupid"

 

[Digital Nigel]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

Yes, me too, really surprised. Even though the workaround works fine for me, Serif really needs to implement a cleaner solution.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

Won't it remember it like other programs do? Is there some way to set it up in the the Preferences?

 

[Jestertheclown]

You'd be wasting your time looking for Affinity Photos 2 in the programmes folder because it isn't there.

Oh dear, now you're really proving you haven't a clue what you're talking about. Not that there was any doubt.

Really?

Then perhaps you'd care to share a screenshot of the programmes folder with Affinity 2 within?

Preferably not one that's been copied and pasted.

"It's good to be . . . . . . . . . Me!"

 

[Digital Nigel]

You'd be wasting your time looking for Affinity Photos 2 in the programmes folder because it isn't there.

Oh dear, now you're really proving you haven't a clue what you're talking about. Not that there was any doubt.

Really?

Then perhaps you'd care to share a screenshot of the programmes folder with Affinity 2 within?

Preferably not one that's been copied and pasted.

Surely even you know that isn't how the fix works? You mean you're posting all these stupid comments without even looking at the simple batch file solution? Really?

"It's really bad to be stupid, ignorant and obnoxious!"

 

[Jestertheclown]

Surely even you know that isn't how the fix works? You mean you're posting all these stupid comments without even looking at the simple batch file solution? Really?

There's no need for you to, as is usual when you can't think of anything worthwhile to say, fall back on snide remarks, sarcasm and insults.

I'm not remotely interested in your fix or how it works as I've no need to use it.

My point, which you're either unable or deliberately trying not to understand is that you posted a quote in which it was stated that it was necessary to go into the Windows programmes folder to locate Affinity Photo 2.

I simply pointed out that that won't be possible because Affinity Photo 2 isn't in there.

Nothing whatsoever to do with your 'fix.'

Simply pointing out an error in your quote.

Nothing more sinister than that.


"It's good to be . . . . . . . . . Me!"

 

[IanYorke]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

 

[jfriend00]

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

Won't it remember it like other programs do? Is there some way to set it up in the the Preferences?

No, Capture One v22 uses it's own plug-in to manage external editors and it does NOT remember things you manually select. Dumb design, IMO.

 

[s_grins]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

I do understand that in situations when your image software refuses to open an affiliated software, you can right-click on file, you want to open, select "open with" and point on Affinity, and Operating System does the job.

OK, I have Affinity 2 recently installed on W11 Pro OS via download from website, and W11 perfectly follows the order and opens Affinity. No problems here

 

[maltmoose]

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

Won't it remember it like other programs do? Is there some way to set it up in the the Preferences?

No, Capture One v22 uses it's own plug-in to manage external editors and it does NOT remember things you manually select. Dumb design, IMO.

 

[Digital Nigel]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: Why are we using MSIX for Windows installers?

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

I do understand that in situations when your image software refuses to open an affiliated software, you can right-click on file, you want to open, select "open with" and point on Affinity, and Operating System does the job.

OK, I have Affinity 2 recently installed on W11 Pro OS via download from website, and W11 perfectly follows the order and opens Affinity. No problems here

There's no problem manually opening AP2 in Windows 10, either.

The problem (now solved with the simple batch file workaround) is to get other programs to invoke it, and to then remember how. So, for example, if you want FastStone to offer it as an external editor when you right-click on an image file, there's no obvious way to set up the link. Finding the hidden AP2 exe file with the obscure name seemed like the solution, but it isn't. But, luckily, some clever soul devised a neat, simple, workaround.

For example, I now have PhotoLab set up to export to Ape:

 

[IanYorke]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

I do understand that in situations when your image software refuses to open an affiliated software, you can right-click on file, you want to open, select "open with" and point on Affinity, and Operating System does the job.

OK, I have Affinity 2 recently installed on W11 Pro OS via download from website, and W11 perfectly follows the order and opens Affinity. No problems here

There's no problem manually opening AP2 in Windows 10, either.

The problem (now solved with the simple batch file workaround) is to get other programs to invoke it, and to then remember how. So, for example, if you want FastStone to offer it as an external editor when you right-click on an image file, there's no obvious way to set up the link. Finding the hidden AP2 exe file with the obscure name seemed like the solution, but it isn't. But, luckily, some clever soul devised a neat, simple, workaround.

For example, I now have PhotoLab set up to export to Ape:

View attachment 3248321

On the Affinity forums they say they will have an official fix early next week. I think it's a simple .exe file that basically does what the .bat file achieves.

Ian

 

[Digital Nigel]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

I do understand that in situations when your image software refuses to open an affiliated software, you can right-click on file, you want to open, select "open with" and point on Affinity, and Operating System does the job.

OK, I have Affinity 2 recently installed on W11 Pro OS via download from website, and W11 perfectly follows the order and opens Affinity. No problems here

There's no problem manually opening AP2 in Windows 10, either.

The problem (now solved with the simple batch file workaround) is to get other programs to invoke it, and to then remember how. So, for example, if you want FastStone to offer it as an external editor when you right-click on an image file, there's no obvious way to set up the link. Finding the hidden AP2 exe file with the obscure name seemed like the solution, but it isn't. But, luckily, some clever soul devised a neat, simple, workaround.

For example, I now have PhotoLab set up to export to Ape:

View attachment 3248321

On the Affinity forums they say they will have an official fix early next week. I think it's a simple .exe file that basically does what the .bat file achieves.

Yes, I thought it would be something like that. Presumably the redirector visible exe file will get installed automatically in the obvious folder in the Program files?

 

[s_grins]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

I do understand that in situations when your image software refuses to open an affiliated software, you can right-click on file, you want to open, select "open with" and point on Affinity, and Operating System does the job.

OK, I have Affinity 2 recently installed on W11 Pro OS via download from website, and W11 perfectly follows the order and opens Affinity. No problems here

There's no problem manually opening AP2 in Windows 10, either.

The problem (now solved with the simple batch file workaround) is to get other programs to invoke it, and to then remember how. So, for example, if you want FastStone to offer it as an external editor when you right-click on an image file, there's no obvious way to set up the link. Finding the hidden AP2 exe file with the obscure name seemed like the solution, but it isn't. But, luckily, some clever soul devised a neat, simple, workaround.

To have a FastStone as external editor? Why should I? I used to have it as a viewer, but stopped using it long time ago and uninstalled.

For example, I now have PhotoLab set up to export to Ape:

View attachment 3248321

--
If you want to be equal, you have to be better...

 

[Digital Nigel]

There is currently an issue in that AP installs as a "Store" app and that means that the expected .exe file is not readily available. This beaks programs that only allow .exe files to be added for extra functionality eg DXO Photolab "Export to Application", hardware devices like the Stream Deck.

Serif are aware of this issue but have disappointedly come back with "it's up to the other people to find a solution".

Our developers have been investigating this, and have confirmed the following:

Certain applications do not like using the generic %LocalAppData% path, instead please try the following:

• Affinity Photo V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\WindowsAppsAffinityPhoto2.exe
• Affinity Designer V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityDesigner2.exe
• Affinity Publisher V2:
  C:\Users\[USERNAME]\AppData\Local\Microsoft\AffinityPublisher2.exe

They have also confirmed that these are 'execution alias' .exe files, and some third party applications don't yet appear to be compatible with these - unfortunately it is down to each third party app to support execution alias .exe files when launching external applications.

I hope this clears things up!

I can't see the path for Affinity Photo on my Win 10 Pro machine and I have show hidden files selected in File Explorer, how many can see this path?

This incompatibility breaks the workflow in many instances and I would have hoped Serif would have been more supportive. Certainly worth checking if this will impact you.

Ian

What is the purpose (Reason) for installing as a "Store" app ?

This is what Affinity has to say about why they are installing as an MSIX "store" app: https://forum.affinity.serif.com/in...why-are-we-using-msix-for-windows-installers/

From the list, it looks like it was good intentioned, but obviously they missed some compatibility issues with other apps. I think the Affinity folks are more than competent and will get this sorted out in time. I am a bit surprised that this issue didn't arise in their beta testing.

I've had to use the batch file work-around in one place, but haven't figured out how to make things work with Capture One v22 yet other than manually selecting the batch file in the file system (which is quite inconvenient) every time I want to do "Edit With" from inside of Capture One v22.

AP2 worked fine with C1. C1's "Open With" plugin works by automatically registering programs that are registered by the OS as image editors.

Not all programs do this and then you need to use File Manager, right click on a jpg, select "Open With", choose the program that isn't yet registered and after the image has opened, you can close the program and the new program will appear in the "Open With" plugin.

Edit: You do have to reset Windows default program settings.

Ian

I do understand that in situations when your image software refuses to open an affiliated software, you can right-click on file, you want to open, select "open with" and point on Affinity, and Operating System does the job.

OK, I have Affinity 2 recently installed on W11 Pro OS via download from website, and W11 perfectly follows the order and opens Affinity. No problems here

There's no problem manually opening AP2 in Windows 10, either.

The problem (now solved with the simple batch file workaround) is to get other programs to invoke it, and to then remember how. So, for example, if you want FastStone to offer it as an external editor when you right-click on an image file, there's no obvious way to set up the link. Finding the hidden AP2 exe file with the obscure name seemed like the solution, but it isn't. But, luckily, some clever soul devised a neat, simple, workaround.

To have FastStone as external editor?

No, the exact opposite.

Why should I? I used to have it as a viewer, but stopped using it long time ago and uninstalled.

I use it a lot, as a viewer, not as an editor. I launch editing programs from it, including Affinity, the Topaz apps, etc. Currently, there's no obvious way of using Affinity 2 as an external editor from FS and other programs like it. That's what this whole thread is about.

 

[lacogada]

I use it a lot, as a viewer, not as an editor. I launch editing programs from it, including Affinity, the Topaz apps, etc. Currently, there's no obvious way of using Affinity 2 as an external editor from FS and other programs like it. That's what this whole thread is about.

I use FS as my viewer and to launch other programs also.

Was interested in Aff 2, but hesitant now.

Have only skimmed through this repetitive and confusing ( for me ) thread.

Does it make a difference (as it relates to this thread ) if Aff 2 is purchased from the Aff website or through the Mic app store ?

 

[Digital Nigel]

I use it a lot, as a viewer, not as an editor. I launch editing programs from it, including Affinity, the Topaz apps, etc. Currently, there's no obvious way of using Affinity 2 as an external editor from FS and other programs like it. That's what this whole thread is about.

I use FS as my viewer and to launch other programs also.

Was interested in Aff 2, but hesitant now.

The solution wasn't obvious, but someone came up with a very simple workaround that's easy to implement, and works well.

See https://forum.affinity.serif.com/in...oto-2-from-dxo-xnviewmp-art-and-raw-therapee/

Having set up the tiny batch file, I point launcher programs at it:




The FastStone editor launcher settings screen



But it sounds like Serif may have a fix next week that makes the workaround unnecessary (though it will, most likely, continue to work)

Have only skimmed through this repetitive and confusing ( for me ) thread.

Does it make a difference (as it relates to this thread ) if Aff 2 is purchased from the Aff website or through the Mic app store ?

No