Windows 10: Open with - Microsoft WinRT Storage API

Mike-V8 · Sep 25, 2022

Hi,Since my PC updated to Win 11 22H2 Pro, right-clicking on a JPG, one of the options is "Microsoft WinRT Storage API", clicking on this just brings up the error message "Element not found". I can find no way of removing this "open-with" item.Just to clarify, I have seen posts referring to this where it has taken over as the Default app, this isn't the case here, all the files open in the correct default programs as they should. The problem is removing Microsoft WinRT Storage API altogether from the open-with menu.Finally, I had the same issue with a laptop - rolling back and new Windows inst

:)

Brink · Sep 25, 2022

Windows 10 WinRT API Packs released

With the announcement of the release of .NET Core 3.0, we are pleased to announce we have posted on nuget.org the released versions of the Windows 10 WinRT API Pack. The Windows 10 WinRT API Pack allows your WPF or Winforms application to quickly and easily access Windows functionality like Geolocation, Windows AI, Machine Learning, Bluetooth and much more.

Accessing these APIs in your project is as simple as adding the NuGet to your project.

Getting Started

Step 1: Configure your project to support Package Reference

Step 2: Add the Microsoft.Windows.SDK.Contracts NuGet package to your project

Open the NuGet Package Manager Console

Install the package that includes the Windows 10 Contracts you want to target. Currently the following are supported:

Windows 10 version 1803

[table][tr][td]1[/td] [td]Install-Package Microsoft.Windows.SDK.Contracts -Version 10.0.17134.1000[/td] [/tr] [/table]

Windows 10 version 1809

[table][tr][td]1[/td] [td]Install-Package Microsoft.Windows.SDK.Contracts -Version 10.0.17763.1000[/td] [/tr] [/table]

Windows 10 version 1903

[table][tr][td]1[/td] [td]Install-Package Microsoft.Windows.SDK.Contracts -Version 10.0.18362.2005[/td] [/tr] [/table]

Step 3: Get coding

By adding one of the above NuGet packages, you now have access to calling the Windows Runtime (WinRT) APIs in your project.

For example, this snippet shows a WPF Message box displaying the latitude and longitude coordinates:

[table][tr][td]1 2 3 4 5 6 7 8[/td] [td]private async void Button_Click(object sender, RoutedEventArgs e) {     var locator = new Windows.Devices.Geolocation.Geolocator();     var location = await locator.GetGeopositionAsync();     var position = location.Coordinate.Point.Position;     var latlong = string.Format("lat:{0}, long:{1}", position.Latitude, position.Longitude);     var result = MessageBox.Show(latlong); }[/td] [/tr] [/table]

Many partners are already using these NuGet files. If you check out a project that is already using these NuGet packages, see the Microsoft.Toolkit.
Click to expand...

Source: https://blogs.windows.com/windowsdev...acks-released/

Brink · Sep 25, 2022

Introducing the Storage Access API for Microsoft Edge

Today, we’re excited to announce the “first-look” rollout of the Storage Access API in our Canary and Dev channels. For developers, this API allows them to determine whether their access to browser-based storage is restricted by a user’s privacy settings and to request storage access from users if so. This capability can be used to create graceful fallback experiences in cases when storage access may be restricted by features such as tracking prevention in Microsoft Edge. For users, this API provides greater transparency into and control over the sites that are requesting access to browser-based storage that could be used to track their behaviors across the web. This post outlines what the addition of the Storage Access API means for both developers and users.

Developer Experience

Using the Storage Access API is as easy as updating your code to leverage the following new functions:

hasStorageAccess()

Useful to check if access to cookies and other storage exists in the current context.

Returns a promise with a boolean result indicating if storage access exists or not.

requestStorageAccess()

Requires a user gesture to invoke.

Useful to request access to storage for a single third-party context.

Returns a promise that will resolve if access is either available or granted and reject if unsuccessful.

Note: Since we are still gradually rolling out the Storage Access API, it’s possible that you may not have it enabled by default on your device. If you want to test it early, please enable the “Storage Access API” flag in edge://flags.
The usage of these new functions is best demonstrated with an example.

Example:

A social media site, contoso.social, offers sites the ability for developers to embed social media widgets as third-party content on their sites. One site where these widgets appear is www.contoso.example. To offer the ability for contoso.social users to comment on, save, or share contoso.example content with friends, contoso.social’s embedded content needs access to its own storage such as cookies or localStorage in the context of contoso.example in order to associate these actions with a visitor’s account.

Checking for Access:

contoso.social can use document.hasStorageAccess() to see if access to storage already exists and to provide an alternative user experience such as displaying a request to login or request access if not:

Code:

document.hasStorageAccess().then(access => {
if (access) {
// Show UX with access to storage.
} else {
// Show UX for no access.
}
});
Click to expand...

Requesting Access:

If no storage access is currently present, contoso.social can request access during a user gesture. As an example, the onclick handler of a login button could be tied to a request for storage access (see the “User Experience” section below) using the document.requestStorageAccess() method.

Code:

function onLoginClicked() {
document.requestStorageAccess().then(() => {
// Access granted: Safe to access storage now.
}).catch(e => {
// Access denied
});
}
Click to expand...

Sandboxing

The allow-storage-access-by-user-activation token can be used to enable the usage of the API when embedded content is loaded in a sandboxed iframe. In practice, both the allow-scripts and allow-same-origin tokens will also be required as well to ensure the API can be effectively used.

Code:

<html>
<body>
<iframe sandbox="allow-scripts allow-storage-access-by-user-activation allow-same-origin" src="https://constoso.social/embed.htm"></iframe>
</body>
</html>
Click to expand...

As a developer, we hope you will leverage the Storage Access API to create web-based experiences that will continue to be compatible even as browsers place more restrictions on third-party storage.

User Experience

With the introduction of the Storage Access API, you may notice an “Allow cookies and site data?” prompt like the one below when you interact with third-party content such as social media widgets or embedded videos while browsing:

This indicates that the site whose embedded content you’re interacting with (contoso.social in the example above) currently has its storage restricted by Microsoft Edge’s privacy settings and is requesting your permission to access its storage within the context of the site you’re visiting (https://www.contoso.example in the example above). While several types of sites require storage access for legitimate scenarios such as making sure you’re signed in when you expect to be, allowing this access can allow the site requesting it track your activity on the site you’re currently visiting.

Clicking “Allow” will temporarily allow the requesting site access to its storage on the site you were visiting when the prompt appeared. This allowance will last for a 30-day period after which it will automatically expire. Clicking “Block” will prevent the requesting site from accessing its storage on the site you were visiting when the prompt appeared. If you change your mind, interacting with the third-party content a second time will cause the prompt to be displayed again, giving you the option to revisit your choice.

To give you control over any storage access requests you’ve allowed before they automatically expire, you’ll notice a new “Cookies and site data you’ve temporarily allowed” section at the bottom of the edge://settings/content/cookies page. Here, you can review and revoke the storage access requests you’ve granted in a single list:

Community Involvement

We implemented the Storage Access API upstream so that all Chromium-based browsers could benefit from it. We are also actively participating in standardization discussions that are ongoing in the W3C Privacy Community Group to ensure that the API works uniformly across browsers. If you have any feedback on the functionality or capabilities of the API itself, please feel free to join the standardization discussions by filing an issue on GitHub. If you have any feedback on the Storage Access API as it exists in Microsoft Edge, please send us feedback using in-app feedback tool (Alt + Shift + I).

To close, we’d like to thank our friends at Apple and Mozilla for their early work on the Storage Access API and our friends at Google for helping pave the way for getting the API implemented in Chromium. We’re excited for you to try it out and to hear what you think!

– Brandon Maslen, Senior Software Engineer
– Scott Low, Senior Program Manager
Click to expand...

Source: Introducing the Storage Access API - Microsoft Edge Blog

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Brink · Sep 25, 2022

Rust/WinRT Public Preview now available on GitHub

We are excited to announce that the Rust/WinRT project finally has a permanent and public home on GitHub:

GitHub - microsoft/winrt-rs: Rust/WinRT - Rust for the Windows Runtime

Rust/WinRT follows in the tradition established by C++/WinRT of building language projections for the Windows Runtime using standard languages and compilers, providing a natural and idiomatic way for Rust developers to call Windows APIs. Rust/WinRT lets you call any WinRT API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.

The Windows Runtime is based on Component Object Model (COM) APIs under the hood and is designed to be accessed through language projections like C++/WinRT and Rust/WinRT. Those language projections take the metadata describing various APIs and provide natural bindings for the target programming language. As you can imagine, this allows developers to more easily build apps and components for Windows using their desired language. You can then use those Windows APIs to build desktop apps, store apps, or something more unique like a component, NT service, or device driver.

Microsoft has long depended on C++ as the backbone for so much of what we do, but it has some challenges particularly when it comes to security. Modern C++ certainly makes it easier to write safe and secure C++ if you follow certain careful conventions, but that is often hard to enforce on larger projects. Rust is an intriguing language. It closely resembles C++ in many ways, hitting all the right notes when it comes to compilation, runtime model, type system and deterministic finalization. While it has its own unique learning curve, it also has the potential to solve some of the most vexing issues that plague C++ projects, and is designed from the ground up with memory safety and safe concurrency as core principles. For more information on Rust and safe systems programming, check out the Microsoft Security Response Center.

Here below is a simple example of Rust calling a Windows API. The API itself does not matter, but it should give you a sense for how naturally Windows APIs may be called from Rust code. In the following example, we are using the XmlDocument class from the Windows.Data.Xml.Dom namespace to parse and inspect a simple XML document:

Code:

use windows::data::xml::dom::*;

let doc = XmlDocument::new()?;
doc.load_xml(“<html>hello world</html>”)?;

let root = doc.document_element()?;
assert!(root.node_name()? == “html”);
assert!(root.inner_text()? == “hello world”);
Click to expand...

If you are familiar with Rust, you will notice this looks far more like Rust than it looks like C++ or C#. Notice the snake_case on module and method names and the ? operator for error propagation.

Here is another example using the Windows.ApplicationModel.DataTransfer namespace to copy some value onto the clipboard:

Code:

use windows::application_model::data_transfer::*;

let content = DataPackage::new()?;
content.set_text(“Rust/WinRT”)?;

Clipboard::set_content(content)?;
Clipboard::flush()?;
Click to expand...

For a more complete example, I encourage you to have a look at Robert Mikhayelyan’s Minesweeper demo. Robert originally wrote a version of the classic game using C++/WinRT and was able to quickly port it over to using Rust/WinRT. GitHub - robmikh/minesweeper-rs: A port of robmikh/Minesweeper using winrt-rs.

This is a very early public preview, but we have decided to work in the open from here on out. So please give it a try and let us know what you think. We would love the feedback as we continue to develop Rust/WinRT and plan to eventually publish on crates.io. We also hope to provide more seamless interop with existing Win32 and COM APIs including support for the com-rs crate, which supports COM APIs today. GitHub - microsoft/winrt-rs: Rust/WinRT - Rust for the Windows Runtime
Click to expand...

Source: Rust/WinRT Public Preview - Windows Developer Blog

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Open with - Microsoft WinRT Storage API

Open with - Microsoft WinRT Storage API

Open with - Microsoft WinRT Storage API

Open with - Microsoft WinRT Storage API

Open with - Microsoft WinRT Storage API - Similar Threads - Open Microsoft WinRT

Open with - Microsoft WinRT Storage API

Open with - Microsoft WinRT Storage API

a Microsoft WinRT Storage API problem

a Microsoft WinRT Storage API problem

All Default Microsoft Apps are changed to "Microsoft WinRT Storage API"

Open with - Microsoft WinRT Storage API

"Microsoft WinRT Storage API default apps error"

"Microsoft WinRT Storage API default apps error"

"Microsoft WinRT Storage API default apps error"