The points I?ll mention in this post to help quickly start developing your first Win Store App
We will not go throw both models because there are a lot of good articles on the internet describing the differences between them but here is a quick illustration based on my own point of view:
In MVC your controllers (Front Controller) are responsible for getting the data from the view and pass it to your application business logic layer and vice versa.
In MVVM your ViewModel automatically change the view and vice versa so you?re just responsible for ViewModel ? Business Logic integration.
In asp.net if you want to serialize an object you need to add the Serializable attribute to your class.
In Windows Store Apps you add a DataContract and DataMember attribute like in WCF
And here 2 methods will help you in your store app
var _Bytes = Encoding.Unicode.GetBytes(json);
(MemoryStream _Stream =
var _Serializer =
_Stream.Position = 0;
(StreamReader _Reader =
Dynamic type in Store Apps will help much in many ways one of the is getting data from web services
//JObject in Newtonsoft library
dynamic resultObj = JObject.Parse(response);
obj1 = resultObj.Name;
obj2 = resultObj.Address;
I know you?ll tell me that dynamic type is now in asp.net but there are a lot of people still using old .net framework
In asp.net you can connect directly to SQL server but in windows store apps you can't (You may a public web service as broker because in Store Apps if your app is connecting to a local service it won?t be pass in the store validation) but you can use SQLite
in your Store App which provides you a basic DB functionality.
In store app you don?t have the full access throw the file system of the machine like asp.net (Of course if you are an admin in asp.net) there is a restriction in file access as an example you can?t read a file by giving it the absolute location like ?D:\myfile.txt?,
you can access the documents library (My documents) and you need a permission for that or you can access files inside application storage or by file picker
Here is a
code sample for file access
Something to mention is the application settings, app settings is a permanent dictionary for your application Each setting can be up to 8K bytes in size and each composite setting can be up to 64K bytes in actual size.
var localSettings = Windows.Storage.ApplicationData.Current.LocalSettings; // Create a simple setting localSettings.Values["exampleSetting"] = "Hello Windows"; // Read data from a simple setting Object value = localSettings.Values["exampleSetting"];
var localSettings = Windows.Storage.ApplicationData.Current.LocalSettings;
// Create a simple setting
// Read data from a simple setting
Object value = localSettings.Values[
Maybe you can use the app settings instead of DB session.
Windows Store Apps has its own design guide lines which will help you to get start with the perfect controls and application scenario for you. One thing I always say in my Design Guidelines sessions is that I want the consumer to feel like he took a deep
breath once he saw your application.
Those links will help you to get started with Windows Store Apps design Guide lines
And about the animation there is a build in animations in some controls like GridView drag and Drop , Delete and Add , etc?
But What I?m talking about is to make a good use of the animation library in Windows Store App.
There are four type of animation :-
And here are three types of content transition and entrance transition I usually use
And for more about animation check this link.