[WCR Sample] Single dotnet run with unpackage selfcontained as example. (#447)

yeelam-gordon · web-flow · commit cdf6aec591d1 · 2025-04-22T08:56:08.000+08:00
* Combine unpackage and selfcontain as single dotnet run command as example
diff --git a/Samples/WindowsCopilotRuntime/README.md b/Samples/WindowsCopilotRuntime/README.md
@@ -39,17 +39,12 @@ join the [Windows Insider Program](https://insider.windows.com).
 # Contributing to this project
 - Refer to the [contributing guide](./Contributing.md)
 
-## Special Considerations for Debugging as an Unpackaged App in Visual Studio
-
-- This project is not designed to be fully functional in an unpackaged app. However, Windows Copilot Runtime does support unpackaged app.
-- To enable proper startup as an unpackaged app, you need to bootstrap the Windows App SDK either Programmatically or By adding the following configuration to the `.csproj` file during the build process:
- ```xml
-  <WindowsAppSdkBootstrapInitialize>true</WindowsAppSdkBootstrapInitialize>
-  <WindowsPackageType>None</WindowsPackageType>
- ```
-- Alternatively, if you are using the Developer Command Prompt for Visual Studio, you can run the app as an ARM64 version using the following command, with the bootstrap property provided:
+## Special Considerations for Unpackaged & Self-Contained Mode with WCR
+
+- This project is not intended to be fully functional when running as an unpackaged app. However, Windows Copilot Runtime (WCR) does support unpackaged apps.
+- Self-contained mode is fully supported by WCR APIs as well.
+- The following command demonstrates how to run the app as an ARM64 unpackaged application in self-contained mode (for both WinAppSDK and .NET):
 ```powershell
-dotnet run -p:Configuration=Debug -p:Platform=ARM64 -p:WindowsPackageType=None -p:WindowsAppSdkBootstrapInitialize=true
+dotnet run -p:Configuration=Debug -p:Platform=ARM64 -p:WindowsPackageType=None -p:WindowsAppSDKSelfContained=true -p:SelfContained=true
 ```
-- Self contained mode is fully supported by WCR apis.     
-- One careful consideration while using self contained mode. The OS ACL permissions prevent it to run inside any folder in `C:\Users` like `Downloads` because `WorksloadsSessionManager` running as a local service, cannot load WCR dlls from that folder with default permissions. This is by security choice, by design. The two ways to solve it are a) Move the self contained folder out of `C:\Users` where ACLs are not too restrictive or b) provide Local Service to access the said self contained folder within `C:\Users`. Only affects self contained mode, it doesn't affect other config modes.
+- One careful consideration while using self-contained mode. The OS ACL permissions prevent it to run inside any folder in `C:\Users` like `Downloads` because `WorksloadsSessionManager` running as a local service, cannot load WCR dlls from that folder with default permissions. This is by security choice, by design. The two ways to solve it are a) Move the self-contained folder out of `C:\Users` where ACLs are not too restrictive or b) provide Local Service to access the said self-contained folder within `C:\Users`. Only affects self-contained mode, it doesn't affect other config modes.
