Before you start, please, download and install the latest Entity Framework version.
Let’s use an existing AdventureWorks Sample database, which is available here http://msftdbprodsamples.codeplex.com/
Generate DataModel from the existing AdventureWorks database.
Want your own data provider be available in the Designer?
Let’s review how it’s possible on the example of mysql.
In order to get it work you need to perform the following steps:
First of all, we need to know how it works. This feature uses Reflection in order to create a list of available data sources. During design time, current assembly is not loaded, so we have to take care about putting our own DataSource implementation in the separate library.
Cache is an important part of the reactive application. Let’s imagine that we don’t have any cache on the server side. In that case every request for every page of your report will cause document rendering. Some documents can be rather huge and it’s not efficient to call document rendering. In the ideal situation we should call document rendering once. On the other side we shouldn’t think about cache like about durable storage on the server side.
We have several implementations of cache on the server side. You may use them in your applications. Their names are SessionCache and AspNetCache. SessionCache as you can guess is based on session as well as AspNetCache based on the AspNet Cache.
Today I’m going to explain how to leverage snapshots feature of Reporting Services in Silverlight Viewer for Reporting Services (version 2.9).
Usually, we have report definition file (rdl) with the specified data source. When we need to display our report, we use the Render method and it causes huge amount of actions on the server side. Reporting Services create query to the data base, then process data and report definition of the report and then we get our report. If you don’t want this routine to happen each time, but to store the rendered report on the server side you may use snapshots. One more use-case when you need snapshots is when you have volatile datasource and you need to store different versions of your report and to get access to them afterwards.
Andrew Kazyrevich (27)
Andrey Akinshin (2)
Darina Merzlikina (1)
Dmitry Zhukov (1)
Eugene Akinshin (7)
Marketing Dept (87)
Mikhail Payson (6)
Sergey Kraynov (3)
Sergey Piskov (9)
Vitaliy Korney (7)