uwp

I'm using the Universal Windows Plataform for making a App and I want to ask how to post data like (id=1) to the server with httpclient. I know that there is some tutorials on internet, but many of them are for Windows 8.1 and don't work in 10. If you want to handle HTTP request in UWP, you need a webservice to support it. If you make a web API project in your solution, then you can use the actions inside controllers to handle the POST request. More reading about web API: click here First you need to install the web API .net Client from NuGet to handle HTTP request from web API. in your UWP

I'm pretty sure that I know the answer to this question (A big fat NO), but is it possible to share downloaded data between the same application but multiple users (Windows login, not Microsoft Store users) in a Windows Runtime environment? The local data folder is relative to each login user, so this seems impossible at first glance. It would be a huge waste for each user to have to download all of the content for the application since it is between 700MB - 1GB of content per app. This accepted answer is outdated. It is now possible to share data between users of a given app in Windows 10, by

It used to be I could cancel the tilt effect on GridView/ListView by editing the item container style and removing the storyboard animations. However, when I edit the templates now on Win10 Universal apps, I am not seeing any of the storyboards. Where can I cancel the animation at? Here's the style that's generated for me (and when used, does not disable animation): <Style x:Key="ListViewItemStyle1" TargetType="ListViewItem"> <Setter Property="FontFamily" Value="{ThemeResource ContentControlThemeFontFamily}"/> <Setter Property="FontSize" Value="{ThemeResource ControlContentThemeFontSize}"/>

[UWP] I have many grids with color binding from App.xaml MainPage.xaml ... <Grid Height="45" Margin="0,0,0,10" Background="{ThemeResource MyColor}"> App.xaml <Application xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" RequestedTheme="Dark"> <Application.Resources> <ResourceDictionary> <SolidColorBrush x:Key="MyColor">#FFFFFF</SolidColorBrush> Then I want to change all of its, in code like this Application.Current.Resources["MyColor"] = new SolidColorBrush(Windows.UI.Color.FromArgb(255, 242, 101, 34)); But it not work.

Imagine the following setup: UWP Library: MinVersion: 10240 TargetVersion: 16299 This library checks at runtime if the UniversalApiContract Version 5 is present. If yes, it will use the new NavigationView control that. UWP App: MinVersion: 10240 TargetVersion: 10240 This app references the UWP Library project. When I run this app on my Computer, which has Windows 10 Version 16299 installed, the following happens: The UWP Library checks at runtime for the api contract. As I have the newest version of Windows 10, yes it is present. Then it tries to create the NavigationView control, and I get a

I have code very similar to this question running in a windows tray application, even with this exact code from the question I get the same behavior. It all works well on classic windows applications, such as Firefox, Chrome, Windows Explorer etc. However when the mouse focus gets to a UWP app such as Edge or Calendar or Mail the scroll becomes jittery and after a few dozen scrolls performed my application hangs and can't even be terminated from task manager (permission denied), this behavior is very reproducible. I'll paste the code from the question here: using System; using System

I'm trying to implement a startup wizard for a UWP application. Preferably the wizard should open in a new window that is non-resizable and located at the center of the screen. I have already tried to use LaunchUriForResultsAsync in order to launch a dummy protocol inside our own app. This way, I could open a new non-resizable window, but it had fixed size (500x500) and position (left side of the main app). Trying to call TryResizeView or to set PreferredLaunchViewSize didn't have any effect, even though they would work within the main (first) window of the same UWP app. I could find only a