I solved this problem by adding Newtonsoft.Json to the NuGet of the startup project (even though it is not directly used in the startup project).
Because there was no solution to this problem, I had to reimplement all paging relevant classes: Page, Frame, SuspensionManager, etc… The solution can be downloaded here: https://github.com/MyToolkit/MyToolkit/wiki/Paging-Overview Update: The page class now also provides the OnNavigatingFromAsync method to show for example an async popup and cancel navigation if required…
CREATOR UPDATE XAML You need to use a component that you put on the background of your app, let’s say a RelativePanel <RelativePanel Grid.Column=”0″ Grid.ColumnSpan=”2″ MinWidth=”40″ x:Name=”MainGrid” SizeChanged=”Page_SizeChanged”/> <RelativePanel Grid.Column=”0″ Width=”{Binding ElementName=MainGrid,Path=Width}” Background=”#28000000″/> <Grid> <!–Having content here, for example textblock and so on–> </Grid> The second RelativePanel is used to set the shadow color above … Read more
My my, look at this here: <UserControl.DataContext> <local:HabitacionControlVM/> </UserControl.DataContext> Someone sold you a bill of dirty, filthy, goods. Probably one of those jerks who run around telling people DataContext = this; is a good idea. Sorry, tangent. Now look at this: <ctr:HabitacionControl Width=”70″ Height=”140″ Ubicacion=”{Binding}”/> What is that I’m seeing? Is that a pseudo-DataContext property? … Read more
That is the complete solution for Windows Desktop: Add the Extension reference “Windows Desktop Extensions for the UWP” like Peter Torr – MSFT mentioned. Use this Code to get the HardwareId: using System; using Windows.Security.ExchangeActiveSyncProvisioning; using Windows.System.Profile; namespace Tobit.Software.Device { public sealed class DeviceInfo { private static DeviceInfo _Instance; public static DeviceInfo Instance { get … Read more
No, you don’t have Trigger support in UWP. A workaround is to use DataTriggerBehavior with a ChangePropertyAction to accomplish the exact same thing. xmlns:Interactivity=”using:Microsoft.Xaml.Interactivity” xmlns:Core=”using:Microsoft.Xaml.Interactions.Core” <Button x:Name=”MyButton” Width=”140″ Height=”80″ IsEnabled=”False”> <Image x:Name=”MyImage” Source=”Assets/xxx.jpg”> <Interactivity:Interaction.Behaviors> <Core:DataTriggerBehavior Binding=”{Binding IsEnabled, ElementName=MyButton}” Value=”False”> <Core:ChangePropertyAction TargetObject=”{Binding ElementName=MyImage}” PropertyName=”Opacity” Value=”0.5″ /> </Core:DataTriggerBehavior> </Interactivity:Interaction.Behaviors> </Image> </Button> Note that you will need to … Read more
The following is probably not complete, but some of the major differences are Old style {Binding } binds to the DataContext binds to a Property Name, flexible about the actual source type New style {x:Bind } binds to the Framework element (code-behind class) needs all types fixed at compile time defaults to the more frugal … Read more
This is an Universal App solution. It’s can view as basically a tutorial on Model, View,and ViewModel. I don’t know what UI Element you want to use, but for this I going to pick a one that is supported in both Windows 8.1 and WP 8.1. The ListView, so in both Project’s MainPage.xaml lets define … Read more
The answer would be no. For further clarifications, best to post on the forum: https://social.msdn.microsoft.com/Forums/windowsapps/en-US/home?forum=wpdevelop Windows 10 introduces several new APIs and concepts (such as API contracts) that are not available on Windows 8.1. An app that relies on such new APIs and concepts cannot run on Windows 8.1. Additionally the app-model and a lot … Read more
With the Windows 10 Fall Creators Update (build 16299) UWP apps can now access SQL Server directly via the standard NET classes (System.Data.SqlClient) – thanks to the newly added support for .NET Standard 2.0 in UWP. Here is a Northwind UWP demo app: https://github.com/StefanWickDev/IgniteDemos We have presented this demo at Microsoft Ignite in September 2017, … Read more