Difference between writing XAML in Metro Apps and standard desktop applications

Question

2.00/5 (2 votes)

See more:

Hi All,

I know this might appear to be a silly question but I'm coming up against some problems developing an app using the Metro framework and I'm looking for a definitive answer as to what the difference is between Metro and desktop application development.

Aside from getting to grips with WIN RT I've hit some snags every time when trying to refresh my memory on how to use little pieces of functionality in XAML. For example, I'm trying to create a continuously fading in and out animation on a button to draw the users attention to that button. So, I can't quite remember how to set up an animation inside a Style. Ok no problem, I check the Google machine with the following search term..

storyboard xaml METRO event trigger

..and get the following result which contains a nice snippet of code for me to hack. Herein lies the problem. This article on MSDN implies you can do this:

<Setter Property="Opacity" Value="0.25" />

     <Style.Triggers>  .......

But this does not compile in my project. As Triggers is not a valid property.

I'm running the same version of .NET and the article does not seem to say you can or can't use this within a Metro app.

- As I say this appears to be a silly question and I can't find a definitive answer anywhere but does Metro have a different flavor of XAML (if that is even the correct way to describe it)?

- What is the proper term to describe this framework so my searches are more effective?

Thanks all,

Larry

Posted 23-Jul-13 3:22am

Laurence1234

Updated 23-Jul-13 3:23am

v2

Add a Solution

Comments

Yvan Rodrigues 23-Jul-13 10:31am

The Style.Triggers element would need to be a direct descendent of a Style element to be valid.

Laurence1234 23-Jul-13 10:49am

Interesting. But in the MSDN article it is not a direct descendant as far as I can see.

Yvan Rodrigues 23-Jul-13 11:12am

Actually now that I looked at the original article, I see it is a direct descendent (2nd child). When you are trying it, is the snippet above wrapped in a Style element?

Laurence1234 23-Jul-13 11:50am

Yes, this was wrapped in the Style element as I was setting it in my standardstyle.xaml.

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Yvan Rodrigues · Answer 1 · 2013-07-23T04:33:00

Solution 1

AS far as the differences go, I have used this guide[^] in the past.

Also when searching for Metro/Windows RT framework-related stuff, often the term Windows Store app yields good results. The fact that they chose to use the term Windows Store to describe a type of application is idiotic, as RT and Metro are better search terms.

Posted 23-Jul-13 4:33am

Yvan Rodrigues

Updated 23-Jul-13 4:35am

v2

Comments

Laurence1234 23-Jul-13 10:50am

This looks like a good start. Thanks Yvan.