Design patterns certainly help for the most part, but what about testing
the styles themselves? Especially for control development, but also for
basic styling on Windows. You want to ensure changing styles hasn't
broken functionality, and it isn't (always) possible to automate tests
for that.
Lookless controls assist greatly with separating the UI from the
functionality, but sometimes the style still effects execution path
(especially extended 3rd party controls).
From: [email protected] [mailto:[email protected]]
On Behalf Of Steven Nagy <[email protected]>
Sent: Friday, 18 June 2010 11:26 AM
To: ozWPF <[email protected]>
Subject: RE: missing resource
I have no specific answer to your exact problem, however I do have to
ask, why are you unit testing the shell?
We have patterns like MVVM for just these reasons; you don't want to
test the UI but the logic behind it.
That said you could always add the style to the Shell.Resources instead.
Steven Nagy
Readify | Senior Developer
M: +61 404 044 513 | E: [email protected]
<sip:[email protected]> | B: azure.snagy.name
<http://azure.snagy.name/>
From: [email protected] [mailto:[email protected]]
On Behalf Of Stephen Price
Sent: Friday, 18 June 2010 12:47 PM
To: ozWPF
Subject: missing resource
Hey all,
Working on some WPF and have hit something I'm sure is easy but can't
seem to find an answer on.
I've added a style to the main page and put the new style into a
MergedDictionary, it works no problems. Where i've come unstuck is
there's a unit test in another project that creates an instance of the
shell. It now fails as it can't find the resource. I'm puzzled at how I
add it. I tried copying the App.xaml file but it gives errors pointing
to the fact the project doesn't like there being an
ApplicationDefinition.
Just wondering how other people get around this?
cheers,
Stephen
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
ozwpf mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
________________________________________________________________________
_______
This email has been scanned by the Bankwest Email Security System.
________________________________________________________________________
_______
_______________________________________________________________________________
Unencrypted electronic mail is not secure and may not be authentic.
If you have any doubts as to the contents please telephone to confirm.
This electronic transmission including any attachments is intended only
for those to whom it is addressed. It may contain copyright material or
information that is confidential, privileged or exempt from disclosure by law.
Any claim to privilege is not waived or lost by reason of mistaken transmission
of this information. If you are not the intended recipient you must not
distribute or copy this transmission and should please notify the sender.
Your costs for doing this will be reimbursed by the sender.
We do not accept liability in connection with computer virus, data corruption,
delay, interruption, unauthorised access or unauthorised amendment.
_______________________________________________________________________________
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
ozwpf mailing list
[email protected]
http://prdlxvm0001.codify.net/mailman/listinfo/ozwpf
