asklar

flowchart TD
A[Is it supported?] --> B{Does it exist?};
B -- Yes --> C[No, it is being deprecated.];
B -- No --> D[Yes, it will be supported soon.];

asklar

// proclist.cpp : This file contains the 'main' function. Program execution begins and ends there.
//

#include <iostream>
#include <Windows.h>
#include <TlHelp32.h>
#include <wil/resource.h>
#include <appmodel.h>
int main()
{

asklar

Sandbox doesn't have the store so you can't install Package Manager through the store You need to download the WinGet msix, but that has a dependency on VCLibs which is also not present in Sandbox.

If you search for VCLibs you get to this download center page: Download Microsoft Visual C++ UWP Desktop Runtime Package

But the link to install the VCLibs package is broken (I hope to have them fix it) so instead you have to download it from this other page: C++ Runtime framework packages for Desktop Bridge

asklar

1. Install the Project System vsix in Visual Studio: open the Extensions menu -> Manage Extensions

2. Restart VS and open the build logging window

3. Clean the project, turn on recording in the build logging window, and build the project

4. You'll see a trace in the Build logging window. You can right click -> open external to open the trace in the binlog viewer.

asklar

Here's a non-exhaustive list of Microsoft UI frameworks in alphabetical order

Adaptive Cards

A cross-platform framework for lightweight UI and data exchange, with multiple renderers (web, iOS, Android, React Native, UWP XAML). https://adaptivecards.io/

Fluent UI

A library for creating apps and websites using the Fluent design languages.

Name	Endpoint	Renders to

asklar

#pragma once
#include <NativeModules.h>
#include <winrt/Windows.UI.Notifications.h>
#include <winrt/Windows.Data.Xml.Dom.h>

using namespace winrt::Windows::UI::Notifications;
using namespace winrt::Windows::Data::Xml::Dom;


REACT_MODULE(Notifications)

asklar

Limiting RN dependencies

Usage in React Native Windows

Today React Native Windows depends on RN core, which uses Folly and a number of other libraries (double-conversion, glog, sys).

Some [parts] of these libraries don’t work in UWP context (e.g. calling CreateFile on arbitrary paths).

We don’t build all of Folly, instead we carve out the minimum set of files that we need (and work in UWP).

Every time we take a new drop of Folly, we are opened up to new dependencies of Folly being introduced (e.g. double-conversion, fmt). These are dependencies of Folly but not used by RN or RNW. However, they are needed to build Folly.

asklar

#include "pch.h"
#include <iostream>

#include <winrt/Windows.Devices.Input.h>
#include <winrt/Windows.UI.Xaml.h>
using namespace winrt;
using namespace winrt::Windows::Foundation;
using namespace winrt::Windows::UI::Xaml;

void printType(const IInspectable& ii) {

asklar

{
  "version": "1.0",
  "components": [
    "Microsoft.VisualStudio.Component.CoreEditor",
    "Microsoft.VisualStudio.Workload.CoreEditor",
    "Microsoft.NetCore.Component.Runtime.3.1",
    "Microsoft.NetCore.Component.SDK",
    "Microsoft.VisualStudio.Component.NuGet",
    "Microsoft.Net.Component.4.6.1.TargetingPack",
    "Microsoft.VisualStudio.Component.Roslyn.Compiler",

asklar

# This script enables or disables VS 2019's JustMyXaml feature
[CmdletBinding()]
param([bool]$Enable)

if (!([bool](([System.Security.Principal.WindowsIdentity]::GetCurrent()).groups -match "S-1-5-32-544"))) {
    throw "Please run this script elevated";
}

$instanceId = & "$(${env:ProgramFiles(x86)})\Microsoft Visual Studio\Installer\vswhere.exe" -property instanceId
$hiveFile = "$($env:LocalAppData)\Microsoft\VisualStudio\16.0_$instanceId\privateregistry.bin"