Silverlight Application Architecture

I was just starting to learn Silverlight, and I'm interested in learning about the typical architecture of the Silverlight application and the workflow in the application (I am using Silverlight 2, but I will move on to 3 soon).

In my test application, I currently have only two default projects - MyProject and MyProject.Web. I am familiar with the MVVM pattern and organized my code using this. However, I had problems understanding what is happening with the client and what is happening on the server, and how to determine this? I assume that the ViewModel layer is on the client - it exchanges data with the model level located on the server. But how will they communicate? Using WCF? Should part of my application be defined in a separate project? And should a part of the client refer to this?

I had problems when I wanted to set up my model to communicate with SQL Server using LINQ to SQL. LINQ to SQL elements do not seem to be allowed in Silverlight projects, and if I add this to a separate class library project, I cannot reference this project from my Silverlight project; "You can only add links to projects of other Silverlight projects in the solution."

All information that would illuminate my understanding of architecture and workflow is welcome. Thanks.

+3
source share

Source: https://habr.com/ru/post/1712608/


All Articles