Xaml on DVLUP

Custom TypingStarted and TypingEnded Events

Thu, 02 Jan 2020 00:00:00 +0000

You know that little indicator in a chat that shows if someone is currently typing? I am working on a new post (coming soon, link will be here) that uses SignalR to communicate who is currently typing in a chat room along with the messages themselves.

To determine who is typing, I use a timer and the TextChanged event. The timer logic itself is straightforward, in the TextChanged event starts a timer.

Talk to the View

Tue, 16 Apr 2019 00:00:00 +0000

There are many scenarios where a UI component might not have a Command or bindable property available for certain features that you need to access from the view model. There is a simple, but powerful, thing you can do to allow this and not break MVVM or testing capability, leverage the Interface.

Scenario

Let’s imagine the scenario where we have a special ListView control that has a HighlightItem method that can only be called with a direct reference to that control. There isn’t a Command or DependencyProperty (aka BindableProperty in Xamarin.Forms) alternative, so it has to be done in the code behind.

Easy XamlCompositionBrushBase

Sun, 18 Jun 2017 00:00:00 +0000

The upcoming Windows 10 update, the Fall Creator’s Update, introduces a new design system, Microsoft Fluent Design System . The design system has 5 major building blocks:

Light
Depth
Motion
Material
Scale

You can use any of these in a multitude of ways, however Microsoft has made it very easy to use in the latest Preview SDK (16190). Some of the things that used to be relatively hard, or at the least verbose, can now be done with a few lines of code.

One XAML for UWP, Windows 8.1 and Windows Phone 8.1

Wed, 27 May 2015 00:00:00 +0000

I was recently involved in a conversation on how to have the easiest way to maintain a XAML view across a UWP (Universal Windows Project) a Windows 8.1 and Windows Phone 8.1 projects. There are a few options and the most straight forward way to do it with a UserControl residing in a Portable Class Library. However…

What if you wanted to have **tailored code for each **without littering your code with #ifdef but still share a XAML view? The XAML View might be what you’re looking for. This is a tutorial on how to do just that. An example project is available for download at the end of the article. Let’s get started:

Custom Pivot Header with Animation

Thu, 09 Apr 2015 00:00:00 +0000

I recently wanted to make a header with tabs for my app’s pages that have a Pivot. Something like Office Mobile, but without the drop-down menus. Here’s the result I got in my upcoming app. I decided to post a tutorial and provide a sample app.

[

Notice the fast fade-in of the background color of the tab, this is important and is where you’ll be able to add your own flavor to the style after you’ve completed this tutorial. Ok, let’s get started!

Invalid XAML error updating from WP7

Mon, 04 Aug 2014 00:00:00 +0000

We are now seeing the beginning of the fast decline of Windows Phone 7 as it exits the market over the next several months, many of you will need to act to update your app to at least Windows Phone 8. I did this for all of my WP7 apps and there was one error that was In just about every upgrade:

An error on this XAML namespace declaration:

xmlns:controls="clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone.Controls"

```Previous to Windows Phone 8, the Pivot and Panorama controls were part of a toolkit. The Windows Phone team did a solid by included these in the OS, they also added new controls like the LongListSelector to replace the toolkit's ListPicker . These controls are now found in the Phone namespace.

It's a very frustrating problem if you're seeing it for the first time. Don't worry, there is a really easy fix... Delete the xmlns:controls line and use only the xmlns:phone one or edit it and remove the ".Contols" part of the assembly pointer. Here is what it will look like after doing the edit option:

xmlns:controls=“clr-namespace:Microsoft.Phone.Controls;assembly=Microsoft.Phone”

Denied?

Thu, 13 Dec 2012 00:00:00 +0000

So, you got an email from DVLUP stating that your challenge submission was denied. Why were you denied? What did you miss? I wanted to write this post to share the top reasons for denial and how to fix it… 90% of these are due to the fact you didn’t edit your WMAppManifest file.

Here are the top offenders:

Not all Live Tiles Sizes
No animated Tiles
Not all WP8 resolutions

#1- You need to have all three tile sizes enabled for your app. Here is a list of the tile sizes from the MSDN Documentation . To rectify this problem, simply toggle the “Support for large Tiles” property in your WMAppManifest file. See the image in answer #2 for more details.