|The technical articles cover a range of survey topics related to various features of Stimulsoft Reports. Interesting and useful tips, hints, how-tos, code snippets etc.|
|1. Steps required for uploading the final version of the product (with Stimulsoft Reports.WinRT assemblies) into the AppStore.
To design and display a variety of reports, different icons are used (indicators, interactions, etc.). Since there is a problem with adding them directly to the assembly (dll), we will store them on the hard drive in a folder given optionally and load them automatically when running the application. The folder will be called StimulsoftWinRT. It is done in order not to increase the size of the final assembly, because there can be problems when testing the final application through the WACK (WindowsAppCertificationKit). Initially the application will search these resources in the folder My Images (our installation will copy them into). The path can be changed optionally by setting the value for the property when loading the application: Stimulsoft.Helper.RT.ResourceLoader.StiResourceLoaderOptions.ResourcesStorageFolder.
When the AppStore will be available for public use, and you will finish your application and be ready for placing it in the store, then, when creating the installation, you will need to add these resources into it, and set in the application the StiResourceLoaderOptions.ResourcesStorageFolder property to Windows.Storage.ApplicationData.Current.TemporaryFolder. Then, when running the installed application, it will seek resources from the folder where the product AppStore is installed.
2. Loading our resources with your application when running.
When loading your application you must load the resources used by our components. To do this, when loading, execute the following code. For the viewer: await StiReportImagesStore.InitStoreAsync(); await StiIndicatorsImagesStore.InitStoreAsync();
For example, you can see any sample (delivered in the installation pack) from the folder Samples. See the sample Demo.RT. In all test samples, we have implemented the application splash screen (Splash\StiSplashControl.xaml), which loads and all the necessary resources. Speaking of splash screens, they are needed in all applications, or you will simply not pass the test through WACK and will not be able to put your application in the AppStore.
3. Additional features of our control.
The pages of Metro application support the AppBar panels which are placed top and bottom of the page. Details can be found here at http://msdn.microsoft.com/en-US/library/windows/apps/hh761499. We use the panels optionally, in order to please all users. Placing our control (StiViewerControl) you can enable or disable integration using the IntegrateToTheTopAppBar and IntegrateToTheBottomAppBar properties. By default, these properties are set to false and integration does not occur, because the user can use them for his/her own needs. Please see the sample IntegrationOfTheAppBarViewerOnTheUserPage delivered with the product installation.