My (and maybe others?) difficulty with MVVM was to understand a simple thing: View knows about ViewModel. I was using bindings and commands, but they are simple strings in xaml. Because of safe resolving at run-time (safe means you can do a typo, but software will not crash) this makes view decoupled from view-model (at … Read more
I bet Eric Lippert will come later and give a better answer, but in case that won’t happen – here is my take, because I also got interested in this. The meaning of “d”, “c” and similar symbols I got from this answer by Eric Lippert. 1) MyProject.ViewModels.SomeViewModel.<OnLogin>d__69.MoveNext() This one is relatively simple. OnLogin is … Read more
The answer provided by @nico has correct statements but made me realize there was more to the issue than I was initially describing. So I cleaned up the question title and question to provide a better question and subsequent answer. Scouring the web I found many of these answers in so many different places, e.g. … Read more
Suspending event won’t fire while you are debugging (but while running your App normal, it will fire just after you navigate away from the App) as it is said also at this blog: …you will wait forever for these to trigger, even though your app switches back and forth to the screen! The reason is … Read more
You can use the CoreApplication class. It provides a static exit method: public void CloseApp() { CoreApplication.Exit(); } However, the documentation states the following: Note Do not use this method to shut down an app outside of testing or debugging scenarios. Sadly, the reason behind that is left unkown. Further more, you can use the … Read more
You can use the CoreApplication class. It provides a static exit method: public void CloseApp() { CoreApplication.Exit(); } However, the documentation states the following: Note Do not use this method to shut down an app outside of testing or debugging scenarios. Sadly, the reason behind that is left unkown. Further more, you can use the … Read more
The SharedSizeGroup is a exclusive to WPF and does not exist in UWP. Goal : create alternative to SharedSizeGroup In order to know the measure, we need to look at all of the controls and find the maximum. What we will be making We use Fody and PropertyChanged.Fody nuget packages. While they are not required … Read more
The UWP platform is only available for Windows 10 devices. We can’t port it back. If you want to use it on a Windows 7 device, you can make a WPF prject, which uses XAML, the same as UWP. WPF can run on Window 7. In particular, the XAML and C# code can be reused.
You can use the following PowerShell command: Get-AppxPackage -Publisher “CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US” | ? {$_.IsDevelopmentMode -eq “True”} | Remove-AppxPackage This does 3 steps: Gets all installed AppX packages published by Microsoft. Filters them by those marked as DevelopmentMode. Removes the results. I just wasted a bunch of time trying to figure … Read more
Try setting PreferredLaunchViewSize in your MainPage‘s constructor like this: public MainPage() { this.InitializeComponent(); ApplicationView.PreferredLaunchViewSize = new Size(480, 800); ApplicationView.PreferredLaunchWindowingMode = ApplicationViewWindowingMode.PreferredLaunchViewSize; } As @kol also pointed out, if you want any size smaller than the default 500×320, you will need to manually reset it: ApplicationView.GetForCurrentView().SetPreferredMinSize(new Size(200, 100));