Sometimes one needs to thank a test, yeah, seriously - in order to gain some order in mind.
The table below, had been taking shape unnoticeably while I was checking tests.
Here comes the result, enjoy!
C# language features classification
... and realizing the internet is flooded with millions (oh really... ;-) of MVVM examples (some are more accurate, others - less), have led me to give you a link which best demonstrates a use of the MVVM pattern (implemented in the purest way of the pattern).
Here it is - MVVM Implementation
Enjoy!
There are several known ways and approaches to implement the MVVM
pattern. I'd like to spec the related 'ingredients' for each element of
the pattern, to make it simplified implemented.
Model
The "Model" mainly represents the BL layer. Actually, it also includes the DAL context of our application.
Here comes:
1. Buisness Logic entities
2. Web Services, WCF connections
3. ADO.NET
4. Database connections
5. Implementation of INotifyPropertyChanged
View
The pure approach for this layer is "DO NOT TOUCH CODE BEHIND", there is only XAML coding.
This layer should contain the "look" of each entity in the Model that comes with a visual context, usually coupled as a User Control or any other visual packaged component.
We may find here:
1. Visual components
2. Visual bindings (binding control to another)
3. Usually includes data templates
4. Bindings to the Model's properties
ViewModel
This is the "glue" between the entity's Model and its View. Its primary role is to be like a gate between the Model, View and the "external world". Any request from/to the "world" would come through this piece of data.
Generally, this part will hold:
1. The entities' collections instances (represented by the full-featured ObservableCollection<T> type, or any other collection).
2. Some wrapping properties which expose the properties of the entity's Model.
3. Any additional logical properties, functions, commands and abstractions which are relevant to maintain the flow of the application.
4. Retrieving data from/to defined connections (WCF, Web Services, DB etc.)
Practical MVVM Pattern
In summary, I tried to highlight some practical known facts about implementing the Model View ViewModel pattern.
Since many examples of this pattern are slightly differentiated one
from another, it is important to give some rules and guides.
In the next post I'm planning to illustrate a simple use of the pattern.
Hope this helps;
Hi there,
I was looking a little around the net to find a good documentation
for the differences between SL and WPF within Microsoft Expression
Blend. But with no success :(
Because it is really important for those who are working daily on
expression blend, let's see what we are able and not able to do by
using Blend and SL/WPF.
As soon as I notice some other differences, I'll let you know :)
Bye,
miridfd
"Silverlight 3 released just over 3 months ago and here we are with yet another release full of features that our community has been asking for" (
Tim Heuer's blog)
Silverlight 4 is nearly here!
Better give
Silverlight 4 beta a glimpse, learn the new, fantastic and helpful features included.
Have you ever converted some text to path? sure you do. You probably encountered the following problem regarding the characters that includes a hole, like 'e', 'R', etc.
To illustrate the problem let's take the word TEAM and convert it to path (I use Expression Blend 3). 
Now, we get the whole text block to be like a vector image, thus enabling us to see the margins of the shapes which the text has converted to.
I'd like to expand the space between the characters. In order to achieve it, let's change to selection tool (V), click on the text, then
We've got five separate paths, a path for each character, as follows
With focus on the 'A', we discover that something has gotten wrong…
Two paths have been created for the 'A'. One for the A and the other for the triangle in the center. In order to fix it, choose the two paths and make sure to click the A's path first, then the little triangle's.
Now, go to the Object menu, Combine->Subtract
Yes! We've got it all right 
You are free to manage the path as desired
