1c5bdfa3cd | ||
---|---|---|
Authoring | ||
Benchmarks | ||
HostTest | ||
Projections | ||
TestComponentCSharp | ||
UnitTest | ||
WinRT.Host | ||
WinRT.Host.Shim | ||
WinRT.Runtime | ||
WinUIDesktopSample | ||
cswinrt | ||
docs | ||
nuget | ||
.gitignore | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
Diagram_AddProjection.jpg | ||
Diagram_CreateProjection.jpg | ||
Directory.Build.props | ||
Directory.Build.targets | ||
LICENSE | ||
README.md | ||
SECURITY.md | ||
STRUCTURE.md | ||
SignConfig.xml | ||
Strings.props | ||
USAGE.md | ||
benchmark.cmd | ||
benchmark_winmd.cmd | ||
build.cmd | ||
cswinrt.sln | ||
get_testwinrt.cmd |
README.md
The C#/WinRT Language Projection
C#/WinRT provides Windows Runtime (WinRT) projection support for the C# language. A "projection" is an adapter that enables programming the WinRT APIs in a natural and familiar way for the target language. The C#/WinRT projection hides the details of interop between C# and WinRT interfaces, and provides mappings of many WinRT types to appropriate .NET equivalents, such as strings, URIs, common value types, and generic collections.
WinRT APIs are defined in *.winmd
format, and C#/WinRT includes tooling that generates C# code that can be compiled into interop assemblies, similar to how C++/WinRT generates headers for the C++ language projection. This means that neither the C# compiler nor the .NET Runtime require built-in knowledge of WinRT any longer.
C#/WinRT Architecture
Component Authors
Component Authors need to build a C#/WinRT projection for .NET5+ targets.
Application Developers
.NET5+ apps reference the NuGet package, which pulls in the projection assembly instead of a winmd.
Motivation
.NET Core is the focus for the .NET platform. It is an open-source, cross-platform runtime that can be used to build device, cloud, and IoT applications. Previous versions of .NET Framework and .NET Core have built-in knowledge of WinRT which is a Windows-specific technology. By lifting this projection support out of the compiler and runtime, we are supporting efforts to make .NET more efficient for its .NET 5 release.
WinUI3.0 is the effort to lift official native Microsoft UI controls and features out of the operating system, so app developers can use the latest controls and visuals on any in-market version of the OS. C#/WinRT is needed to support the changes required for lifting the XAML APIs out of Windows.UI.XAML and into Microsoft.UI.XAML.
However, C#/WinRT is a general effort and is intended to support other scenarios and versions of the .NET runtime, compatible down to .NET Standard 2.0.
Running C#/WinRT
Download the C#/WinRT NuGet package here: http://aka.ms/cswinrt/nuget
Please see usage for details on running the C#/WinRT tool. For additional documentation visit http://aka.ms/cswinrt.
Building C#/WinRT
C#/WinRT currently requires the following packages to build:
- Visual Studio 16.6 (more specifically, MSBuild 16.6.0 for "net5.0" TFM support)
- Microsoft.Net.Compilers.Toolset >= 3.7.0 or Visual Studio 16.8 preview (for function pointer support)
- .NET 5 SDK 5.0.100-preview.5.20279.10
- WinUI 3 3.0.0-preview1.200515.3
Note: As prereleases may make breaking changes before final release, any other combinations above may work but are not supported and will generate a build warning.
The build.cmd script takes care of all related configuration steps and is the simplest way to get started building C#/WinRT. The build script is intended to be executed from a Visual Studio Developer command prompt. It installs prerequisites such as nuget and the .NET 5 SDK, configures the environment to use .NET 5 (creating a global.json if necessary), builds the compiler, and builds and executes the unit tests.
After a successful command-line build, the cswinrt.sln can be launched from the same command prompt, to inherit the necessary environment.
Note: By default, projection projects only generate source files for Release configurations, where cswinrt.exe can execute in seconds. To generate projection sources for Debug configurations, set the project property GenerateTestProjection to 'true'. In either case, existing projection sources under the "Generated Files" folder will still be compiled into the projection assembly. This configuration permits a faster inner loop in Visual Studio.
Note: When building the first time, the build clones the testwinrt project. The build depends on this project, but msbuild doesn't consistently pick up the change when the repo is first cloned repo. You may need to build a second time if this is your first build to address the timing issue.
Please see the repository structure for a detailed breakdown on the repo contents.
Related Projects
C#/WinRT is part of the xlang family of projects that help developers create APIs that can run on multiple platforms and be used with a variety of languages. The mission of C#/WinRT is not to support cross-platform execution directly, but to support the cross-platform goals of .NET Core.
C#/WinRT is also part of Project Reunion - a set of libraries, frameworks, components, and tools that you can use in your apps to access powerful platform functionality across many versions of Windows. Project Reunion combines Win32 native app capabilities with modern API usage techniques, so your apps light up everywhere your users are. Project Reunion also includes WinUI, WebView2, MSIX, C++/WinRT, and Rust/WinRT.
Contributing
File a new issue! This project welcomes contributions and suggestions of all types.
We ask that before you start work on a feature that you would like to contribute, please read our Contributor's Guide.
License Info
Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
Code of Conduct
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.