GithubHelp home page GithubHelp logo

microsoftdocs / winrt-related Goto Github PK

View Code? Open in Web Editor NEW
76.0 44.0 89.0 46.02 MB

WinRT related reference content for developing Microsoft Universal Windows Platform (UWP) apps

License: Creative Commons Attribution 4.0 International

PowerShell 100.00%

winrt-related's Introduction

Legal Notices

Microsoft and any contributors grant you a license to the Microsoft documentation and other content in this repository under the Creative Commons Attribution 4.0 International Public License, see the LICENSE file, and grant you a license to any code in the repository under the MIT License, see the LICENSE-CODE file.

Microsoft, Windows, Microsoft Azure and/or other Microsoft products and services referenced in the documentation may be either trademarks or registered trademarks of Microsoft in the United States and/or other countries. The licenses for this project do not grant you rights to use any Microsoft names, logos, or trademarks. Microsoft's general trademark guidelines can be found at https://go.microsoft.com/fwlink/?LinkID=254653.

Privacy information can be found at https://privacy.microsoft.com/en-us/

Microsoft and any contributors reserve all others rights, whether under their respective copyrights, patents, or trademarks, whether by implication, estoppel or otherwise.

winrt-related's People

Contributors

citelao avatar court72 avatar cxwtool avatar deepakmsft avatar dennislee-dennislee avatar drewbatgit avatar githubber17 avatar grantmestrength avatar jak-ms avatar jdmartinez36 avatar jesbis avatar karl-bridge-microsoft avatar knicholasa avatar ktoliver avatar laurenhughes avatar mcleanbyron avatar mcleblanc avatar mijacobs avatar mikematteson avatar msatranjr avatar oldnewthing avatar prashobnambiar avatar predavid-zz avatar pritamso avatar quinnradich avatar rmca14 avatar steven-clements avatar stevewhims avatar tylermsft avatar v-shils avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

kevinkieselbach andrewleader xiedongweo hpsin tedhudek aaronfriel adambraden nonasi nehinnan johngallardo sbovo mrmxo thomasclaudiushuber andylsn riverar thomps23 nschonni knicholasa mydoc2019 saraclay c-don lifespan mikehillberg mairaw predavid-zz ncastle1 rudyhuyn 13thsymphony ghuntley kevinmiles bogdanmitrache watemlifts eriwong bigbri64 dianmsft weitzhandler hassoon1986 mancunianbandit azurementor fghzxm ptorr-msft huios niels9001 borool hyoshioka0128 rahulkps23 oldnewthing bavi2 adamperes lukepicci djee-ms ismailhassani tfennel defaultryan citelao rdmaclachlan mrfohun87 reflectronic jimleigh spt2kor shakersmsft huzaifa-d tunip3 shkmaano ozsolomon-msft drustheaxe asklar rayiik vessjason76 steven-clements isabella232 github30 bobbytreed tiberiusdraig peterfoot ahmed605 xlinush wcheng-msft dhoehna beervoley saschanaz isanusngh baka632 ho-cooh jofernmorais meltyli dlech poa00

winrt-related's Issues

Namespace link is broken

Namespace links here: http://schemas.microsoft.com/appx/manifest/desktop/windows10/4 but is a broken link.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

dead link

Interfaces; how to implement them in C++/WinRT in See also section is dead.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

What "Remarks section"

The description of the Name element refers to the "Remarks section" but there is no remarks section. Please add a remarks section with further explanation of what the Name element is.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Confusion between Windows.UI.Xaml and Microsoft.UI.Xaml

The Windows UI Library has a nuget package called Microsoft.UI.Xaml

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Absence of PhoneCallManager at Windows Mobile Extension for the UWP ver 10.0.17134.0

[Enter feedback here]

When i add reference "Windows Mobile Extensions for the UWP" ver 10.0.17134.0
accordance with the document for run example code
PhoneCallManager class (withPhoneLine class) was absence.

i think need to change reference version on document or example code properly

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Updated content?

Is this limitations doc still valid in October 2018?
No progresses for these missing features?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Using this library overrides custom accent colors

Adding the required line to the App.xaml file overrides any changes made to the accent color by setting the SystemAccentColor resource.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

What is the purpose of ClassicAppCompatKey?

I thought AppCompat keys were thoroughly deprecated starting with Windows 8 (although I can't find the doc mentioning this right now). The fact that this key is in the rescap4 namespace implies it is not for general use, but on the other hand it is publicly documented here, which implies that might be found useful by a fairly large segment of apps/devs. This article does a good job of explaining what ClassicAppCompatKey is, but does not discuss at all what it does. Could this please be expanded? Thanks!

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Supported Services

Hi!
I have bought a TI CC2650 SensorTag. Using the Bluetooth LE Explorer app from the windows store, I can inspect the service names of my device along with their UUIDs as well as their characteristics.
Upon inspection, I noticed some service names are named as 5digit numbers (ie: 44032).

However, as seen here, only these services are supported.

  • name:battery
  • name:bloodPressure
  • name:cyclingSpeedAndCadence
  • name:genericAccess
  • name:genericAttribute
  • name:glucose
  • name:healthThermometer
  • name:heartRate
  • name:runningSpeedAndCadence

Is it possible to read from services named differently than those from this list?
Thanks!

Update custom audio for UWP desktop

In the "Remarks" section:
"UWP apps that target the desktop platform don't currently support custom sounds; instead, you can choose from the list of winsoundevents."

Proposed change:

"UWP apps that target the desktop platform prior to Version 1511 don't support custom sounds; instead, you can choose from the list of winsoundevents."

Also add that information into the "Attributes & Elements" table at the end of the "src Attribute" description, i.e. below the "On Windows Phone 8.1" part.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Reversed UsagePage and UsageId in the examples

Hi! In the code snippets above, for gamepad and joystick, the UsagePage and UsageId should be reversed in the <Function> tag (so that to follow the format usage:"UsagePage UsageId"). More exactly, for a gamepad, the Type should be usage:"0x0001 0x0005" (or usage:"0x0001 *" if using the format from the examples).

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Controls with *Reveal* Background have just white background with both light and dark themes

Project settings: 15063-17713/17134

I added a button with one of the Reveal backgrounds.

This bug appears on desktop(17713.1000) after I add some items to controls:NavigationView(settings item doesn't have any effect in this case).
This situation always exists on mobile(15254.490) even if there is only button with reveal background.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

method name generation algorithm is incorrect

It's for the first entry. Subsequent entries are the first numeric value which has not already been used.

So you have LineHeightProperty, then LineHeightProperty2, LineHeightProperty3, etc.

If you have LineHeightProperty and LineHeightProperty3, then the overloads of LineHeightProperty will be named: LineHeightProperty, LineHeightProperty2, and LineHeightProperty4 (since LineHeightProperty3 already exists).

The same algorithm applies to interface names.

MainPackageDepencency is not documented, part of optional packages/related sets

I found searching for "MainPackageDependency" from https://docs.microsoft.com/en-us/windows/uwp/packaging/ does not produce any results.

But I did find this documented here: https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/element-uap3-mainpackagedependency-manual

Seems the index needs to be updated.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Usage examples

Would be nice to see an example in C++/winrt showing an array_view being constructed, loaded with data, accessed. The above example merely shows the templates.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Documentation for PhoneProductId and PhonePublisherId is incomplete.

The documentation explains, what values to choose for the PhoneProductId and PhonePublisherId, in case the package is an update to a Windows Phone app. It does not explain, what values to use in case the app is not an update, but rather a new UWP app.

This information is needed by developers, that cannot use the New Project templates in Visual Studio, authors of Visual Studio extensions, or vendors of project generators (such as CMake).

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

this schema is stored in AppxManifest.xml files in the .appx file and files with .appxmanifest in source

This page should explain the names of the files and file extension used to identify files that contain xml that follows this schema to make it easier to relate those files and this documentation. For example in the .appx file this schema is stored in a file named AppxManifest.xml.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Missing info regarding how ValueName field can be used

An important piece of information that should be explicitly documented is what format the markup should take if you are specifying a default key value (i.e. a value that in .reg format would be named '@'). I ASSUME that I should just leave the ValueName attribute off and provide a Value, but I wonder if instead I should use ValueName="@" or ValueName="" (I assume not the latter because the specification says it must begin and end with a non-whitespace character, and this does neither). Anyway, it's ambiguous.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Invalid Cast Runtime Exception

I just installed the nuget packages and added the resource dictionary. I have a method that returns a Brush:
return (AcrylicBrush)Application.Current.Resources["SystemControlAltMediumLowAcrylicElementMediumBrush"]

It throws: "System.InvalidCastException: 'Unable to cast object of type 'Microsoft.UI.Xaml.Media.AcrylicBrush' to type 'Windows.UI.Xaml.Media.AcrylicBrush'.'"

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Incomplete 1809 AppInstaller documentation

1809 AppInstaller content is incomplete as of commit 3d27b6c

  • AutomaticBackgroundTask, ForceUpdateFromAnyVersion are not documented correctly (e.g. wrong namespace)
  • AutomaticBackgroundTask, ForceUpdateFromAnyVersion link to the wrong content
  • HoursBetweenUpdateChecks is confusingly a String (0-255) inclusive in some spots and Integer (0-24) with unknown (ex|in)clusivity – which is it?
  • Examples are unusable, have code formatting issues (https://docs.microsoft.com/en-us/uwp/schemas/appinstallerschema/element-onlaunch#examples)

cc: @mikematteson

RefreshContainer throws exception

Attempting to use RefreshContainer via this library results in Could not find Windows Runtime type 'Microsoft.UI.Private.Controls.IRefreshInfoProvider when using the RefreshContainer via XAML.

I assume this should be supported given I can see nothing to say it shouldn't be

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Where is the Holographic Extension SDK?

The holographic device family is missing. Not only here, I'm also having trouble finding related contracts and headers on disk in the SDK (e.g. Windows.Perception.Automation.Monitoring.PerceptionAutomationMonitoringContract).
Is that intended or a mistake?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Cant create APPX with Microsoft.UI.Xaml

Hello!

I using Windows Application Packaging Project for pack UWP-application with native background app service. UWP application uses Microsoft.UI.Xaml.
When i try to create APPX of my Package project I get these errors:

image

Debug appx creates successfully but Release no. Can you help me to fix this?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Does the unsupported service list need's to be updated?

I see in the next post (https://support.microsoft.com/en-us/help/10568/windows-10-supported-bluetooth-profiles) that some profiles are now supported, like A/V Remote Control, does the unsupported service list has changed or not?

The list of unsupported services is here -> https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-specify-device-capabilities-for-bluetooth#support-for-bluetooth-rfcomm-services

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

AcrylycBrush FallbackColor Warning

I have warning when I use Microsoft.UI.Xaml.Media.AcrilicBrush:
<winui:AcrylicBrush TintColor="{ThemeResource PopupsBackgroundColor}" FallbackColor="#d8000000" BackgroundSource="Backdrop" TintOpacity="0.5"/>

The property ‘FallbackColor’ on type ‘AcrylicBrush’ is not available in the target platform minimum version (10.0.14393.0) supported by this project.

Is this suppose to work this way?

Formatting on ISF page did not translate well from PDF

Table format is significantly more difficult to read in the HTML documentation than the original PDF, including some errors e.g. in the Word Example under the TAG_DRAW_ATTRS_TABLE, TAG_PEN_WIDTH, the value 3 is displayed with confusing bullet points and disconnected from its tag.

Also the syntax highlighting was lost in several locations.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Description in "Command"-Section is wrong.

A Command can contain 1 up until 20 ListenFor-Statements, like descriped in "ListenFor"-Section.
Also the error in the Code show's that a Command can only contain 10 ListeFor-Statements, if you add 21 Listen-For Statements. Please fix in new Version.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

The IgnorableNamespaces attribute description isn't quite right.

The documentation reads:
"Declares namespaces used in the manifest that should be ignored. Ignored namespace elements are not validated and should be considered untrusted. Multiple namespaces are specified with a space between each namespace."

This isn't exactly correct.

According to a manager at Visual Studio, "Ignorable namespaces are only ignored if they are not understood. If the current system understands the namespace, the elements in it will be processed. Because TPMinV can be less than TPV, if TPV elements were to be deployed to a TPMinV system, deployment would fail. To prevent that, the new elements are tagged with an ignorable namespace so that downlevel systems don't fail. Technically, if TPV == TPMinV, there shouldn't be a need to put anything in the ignorablenamespaces attribute. Validation should occur against everything the system understands regardless of whether it is ignorable or not."

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Namespace Requirements incorrect.

It looks like the Namespace is incorrect. It should be rescap3.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Developers who are not in the Windows organization should never use the [contract] attribute.

The [contract] attribute is an artifact of the mechanisms that the Windows organization uses to implement our versioning story and manage the process of creating multiple editions of Windows. There is no scenario for a user outside the Windows organization to use contract attributes. The reason you see this in the auto-converted IDL files is because the base IDL files for those are from the internal-to-windows sources.

Inverse to `winrt::get_abi()`?

I wanted to investigate ABI – C++/WinRT interop and found the get_abi documentation.

I also know of an interoperability page in the C++/WinRT GitHub docs (that I think may be outdated?)

I would expect a related link on the get_abi page that would show the converse: converting ABI classes into C++/WinRT classes (just like we have for CX).

Is there a page explaining this interop? I could not find one. Thanks!

Is it BundleManifest.xml or AppxBundleManifest.xml?

this page mentions BundleManifest.xml as the name of the file in the .appxbundle but I understand AppxBundleManifest.xml is the right name. please update this page if I have this right.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Windows.Foundation.Metadata.ApiInformation.IsEventPresent("Windows.UI.Xaml.Controls.TextBox", "CopyingToClipboard") is returning true even though the event is not available in ApiContract v3.0.0 (i.e.,Windows SDK v 10.0.14393)

Hello,

I am developing an UWP Application with Visual Studio Community 2015 installed in a machine with Windows 10 OS build 17134.228 (version 1803). I have install only one sdk which is 10.0.14393.33. The application is targeted to 14393 as max version and 10240 as min version.

In MainPage.xaml.cs, I am simply invoking the below code inside MainPage constructor after InitializeComponent:

public MainPage()
{
    this.InitializeComponent();
    if (Windows.Foundation.Metadata.ApiInformation.IsEventPresent("Windows.UI.Xaml.Controls.TextBox", "CopyingToClipboard"))
    {
       System.Diagnostics.Debug.WriteLine("TextBox.CopyingToClipboard event is present");
    }
    else
    {
       System.Diagnostics.Debug.WriteLine("TextBox.CopyingToClipboard event is not  present");
    }
}

In the above case if statement should fail as the application is targeted to 14393 where the CopyingToClipboard event is not present and "TextBox.CopyingToClipboard event is not present" should be printed to output console.

But, that is not happening, the if statement is being passed and "TextBox.CopyingToClipboard event is present" is being printed to output console.

Can anyone please help me with this issue?

Microsoft.UI.Xaml.dll calls an unsupported API

Submitted my app using Windows UI Library for certification. But certification failed saying that "API CoIncrementMTAUsage in ole32.dll is not supported for this application type. Microsoft.UI.Xaml.dll calls this API". Is there anything I missed? I saw the doc says the library is ready for store submission.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Microsoft.UI.Xaml breaks down RevealBackgroundBrush

Hello!
I try to use Microsoft.UI.Xaml in my project, however I found some bugs: RevealBackgroundBrush isn't working properly in a custom ControlTemplate.

XamlControlsResources is disabled in App.xaml.cs:
image
And enabled:
image

I created the example project for this bug.
RevealBug.zip

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

a few problem of NavigationView with winui library

a few problems with the new NavigationView control on winui library :

  1. No Acrylic.
  2. No way to manually set acrylic because there is no "PaneBackground" property.
  3. No way to edit its template in blend either.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Contradiction between schema version and Windows version

In the Attributes and Elements section, you say the 2017 schema is between 1709 and 1803 and in the Requirements section you say the 2017 schema is for version 1709 and later (no upper limit). Which one is true?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

__forceinline

cppWINRT is using always the latest MSVC C++17, is __forceinline actually necessary?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Adding arbitrary XML elements

The schema doesn't include mention of adding arbitrary XML elements.

If I add arbitrary XML data to the toast payload (for example, adding a <data>Foo</data> element inside <toast>), I've found that it will successfully be passed through the OS and on to the app. Is this undefined behavior or can we rely on it? It's potentially useful for including metadata that client apps can process further.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Is this meant to be used alongside Windows.UI.Xaml.Controls, or instead of Windows.UI.Xaml.Controls?

I understand this library is meant to "fill the gap" for developers wanting to use newer controls on older Windows 10 builds (so that they get a larger audience).

Looking at the features mentioned at https://docs.microsoft.com/en-us/uwp/toolkits/winui/, one could draw the conclusion to use all controls from these Nuget packages instead of directly referencing the Windows controls and only using these Nuget packages as a fallback for older OS builds, since this seems much easier than using the version checks to decide what control or features to use.

Could you please clarify in what cases one would still use the built-in Windows controls and rely on version checks, rather than using this library?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Updates and Changelogs

Would it be possible to include the latest versioning for the Windows UI Library here? And include changelogs detailing what has changed. As these are not open source right now, it is important to find a way to detail new features in the future, or breaking changes.

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

XamlDirect link needs updating

Does link need to point to https://docs.microsoft.com/en-us/uwp/api/microsoft.ui.xaml.core.direct.xamldirect rather than the old windows.ui.xaml... namespace?

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Windows.ApplicationModel.Calls.CallsPhoneContract is available in desktop mode, but it isnt considered at documentation

I'm developing an app for Windows 10 Mobile and Desktop devices, and I just found out that if you do have Skype installed on your desktop and also have a microphone this contract is available in Desktop mode, so the only exclusive contract for a windows phone is "Windows.Phone.PhoneContract".

I'm posting here this because it seems that in you documentation "Windows.ApplicationModel.Calls.CallsPhoneContract" is also exclusive for mobile devices. I'm just testing my app and this line of code "ApiInformation.IsApiContractPresent("Windows.ApplicationModel.Calls.CallsPhoneContract");" is throwing me a true boolean value.

Hope this feedback get updated!!!

If you need more information dont hesitate to contact me "[email protected]" i'll be glad to help!!!

I'm also adding this screenshot of my desktop app, where i'm showing how checking if the api is present in my desktop, I assume because my laptop has a microphone integrated and also have skype installed.

I thought this contract was exclusively to windows phone, I changed my code to the following contract to ensure my adaptative code work just on windows phone. in the screenshot i show the results of my debugging also the information of my OS and Laptop.

image

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

What is uap6:AllowExecution used for?

Title really says it all. Why would you want to use this element in your AppX manifest, if it renders that AppX seemingly useless? Some context would be helpful here.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Manifest documents should link back to feature documentation

Each manifest page should have a related topics section which links back to the corresponding feature page. These manifest schema pages are pretty useless to actually understand how to use the feature, but they usually come up first in search results. For instance, this file type association schema page should link to the feature docs here (it should also link back to this schema page).

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Doesn't seem to work. :(

I followed all the steps mentioned in this doc. But building the project in Creators Update still gives me an error that says NavigationView is not supported in API version 4.0.0.0. Am I missing anything?

Project built on Windows 10 version 1803.
MinTarget: 1703
MaxTarget: 1803

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Where on disk do the SDK API contracts reside?

I am using SandCastle (originally created by Microsoft and now managed as an open source project: https://github.com/EWSoftware/SHFB) to document a UWP based API. The problem is that SandCastle cannot figure out where the Windows Universal Platform SDK API contracts live on disk to complete its reflection-type interrogation. I am particularly interested as to where the following Assembly references can be found on disk: Windows.Foundation.FoundationContract, version=3.0 Windows.Foundation.UniversalApiContract, version=5.0. I have the Windows 10 Fall Creators Update Universal SDK (version 10.0.16299.0) installed.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.