Windows AI Api for unpackaged apps

[awrff]

Hi team and everyone,

I created a unpackaged WPF app and call Phi-Silica api in it, trying to see if it's feasible. I followed the documents and use <WindowsPackagedType>None</WindowsPackagedType> to ensure WindowsAppSDK runtime can be properly loaded. This indeed work, but the app encountered Access Denied exception when I actually call LanguageModel.

My question is -- Does Windows AI Api suppport unpackaged apps or not?

If it does support, how to bypass the package identity verification. If not, is there any solution if I just want to build a background service with phi-silica ability and provide interfaces to other host process?

[castorix]

In MSDN at : https://learn.microsoft.com/en-us/samples/microsoft/windowsappsdk-samples/windowsaisamples/ ,
there is :
"Unpackaged app configuration is no longer supported. Every app using Windows AI apis must have a package identity which can be granted to apps with an external location to achieve that with unpackaged binaries."

[awrff]

Yeh...I saw this too. I think I just got confused when I saw this doc. I thought by using the bootstrapper way to load Windows App SDK runtime, even the unpackaged app could use phi-silica.

[awrff]

So the relationship between them should be: Windows AI API is just part of the Windows App SDK. To use Windows AI API, package identity is necessary. (Correct me please if I was wrong)

[RDMacLachlan]

You are correct, the Phi Silica APIs are part of a Limited Access Feature (see LimitedAccessFeatures class). Your app must meet the identity requirement to use these APIs.