One of the unwritten rules in MVC is that ViewModel classes should be kept very simple. They should basically represent data to be displayed in your views. Then, depending on the concrete implementation and the requirements, the whole mapping and connecting it all together part does not always stay simple.
The usage of ViewModels in DD4T 2.0 can actually be very simple, as the example code will try to show. Anything with a simple basis should be also extendable in an easy way and that is the main goal of the framework.
One of the deployment scenarios with DD4T 2.0 is to use a REST service. There are many advantages attached to this approach, but you have to be careful about one thing: the number of TCP connections between the web server and the REST server. In this article I will discuss the cause and provide a solution. Continue reading
This post is part of a series. In the previous article I explained how you can create your own ViewModels in a few minutes.
In this post we will look at number and date fields. We will also learn how to model multiple value fields and metadata fields.
This post is part of a series. In the previous article I explained what ViewModels are and why they are useful. I imagine you are all excited about this, so let’s see how you can create your own ViewModels in a few minutes!
One of the most useful novelties in DD4T 2.0 are the ViewModels. A ViewModel is a simple class, normally consisting only of properties, which is handed over to a view for rendering.
In this small series – published daily until Christmas – I will explain what view models are, how you create them and how you can use them.