This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(256, 33%, 34%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERM%3C/text%3E%3C/svg%3E)
ok, we have this here
1) https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/tutorial-unpackaged-deployment
this tells me, that I have to use "MddBootstrapInitialize" before I can use things from the App SDK (like WinUI 3)
and we have this here
telling me, that I need an "install-time reference" and a "install-time reference" ... which would be done using
"MddTryCreatePackageDependency" and "MddAddPackageDependency"
The question now (because all tutorials I found confuse me)...
Does MddBootstrapInitialize call MddAddPackageDependency? Or do I have to call both? Or just one? Which one? Why? ... what's the correct way of using these functions???
Rudolf
Since the 1.0 Stable Release, I don't use BootStrap anymore for Unpackaged apps
I just follow Create a WinUI 3 app
? ... but, don't you then end up with a packaged app?
No, they added :
<WindowsPackageType>None</WindowsPackageType>
Before, you had to remove the package and use MddBootstrapInitialize to be able to use XAML controls and everything else without the package
ok... sounds interesting... I will try this ;-) ... thanks a lot
in my opinion the documentation is a mess... "how to create an unpackaged app?" ... create a packaged app and set the values to "none" by editing the raw file? ... and then see the "other documentation" "showing how to use bootstrapper in order to use ... in an unpackaged app?" ... and then? should I ignore it because I don't need it? so why do they mention it? ... and does it work on 10 or only on 11? who knows... that's all a mystery...
but way back in time, when COM and DCOM was still the latest technology, it was exactly the same mess... instead of saying -> those 3 commands are the absolute minimum you have to call, they always showed examples with hundrets of lines of code and the typical Microsoft-mess with a variable definition that's defined by something that's defined by two other things and then defined by a third thing which is defined by a fourth thing and in the end is defined as an empty variable and thus dissolving to nothing...
Yes, it is not very clear...
It is because there have been many preview versions and the documentation has not been updated regularly
As I tested most of versions, I know how it works now, but I spent time to solve all the configuration problems on the first versions, in particular for unpackaged apps
(and there are still several bugs, sometimes in C#, other time in C++)
(bugs are reported here : issues and MS developers are also here : discussions)