I have an RDLC-report which contains a lot of small images (hundreds).
When I'm opening it using SSRS-portal it groups all images into one sprite, loads it in one call and opens fast.
But if I embed it into my asp.net mvc application via iframe using ReportViewer control from Microsoft.ReportingServices.ReportViewerControl.WebForms package, it simply loads each image separately (making hundreds of calls) and opens very slow.
I'm using the last version of the ReportViewer control now - 14.0.0.0. But also I've tried older versions without success.
Except this there is no more difference working with this report via SSRS-portal or via my own portal.
Does anybody know how to force it use sprites instead of separate images when you embed it into your own portal?
After some research I've found that it seems to be a known issue.
Such optimization of images presents in native mode (e.g. when you're using SSRS-portal) and doesn't present in integrated mode (e.g. when you embed report into your portal).
Here are the links where I've found the most important information:
What’s Up With the Slow SSRS R2 Rendering in SharePoint 2010 Integrated Mode?
The switch back to SSRS Native mode for Performance Reasons
SSRS 2008 R2 Add-in Performance Issues
Related
I am trying to use Google.Apis.Analytics.v3 for the 1st time, programmatically. We are building dashboard pages to show statistics, within their organisation-until now I have been reporting on information from internal databases.
Now we want to retrieve data from our Google analytics account.
My main tool for development is visual studio and C#. Some of the webpages have been created just using text editors, by a colleague, but I'm happier doing it in visual studio. We are sharing this development with organisations who do not use visual studio. So when I finish work on my webpages, we make 2 small changes to my files and we can be used without needing visual studio.
I have experience also in JavaScript and some jscript. I did find the Google API nuget package for studio and have installed it (not had time to look at it yet).
Some options Google have on their help site involves languages such as Java that we don't have any experience of in the format they appeared to be using it.
Given the above, can someone advise or recommend the best approach I should take for retrieving Google analytics data into our webpages (I do not want users to have to login-it should just seamlessly retrieve the data and display it).
Thanks
You could make an MVC project, where you can take the data and display it in a View. Here you can see some example with GoogleApi and MVC project in C#.
This might be a really easy question for the guru's in stackover flow but i am not sure how to approach it.
Migrating from Desktop Application to Web Applicaiton
Used C# for Desktop Application
Used Asp.net for Web Application
first i created the desktop application but due to the time constraint on installing it on several machines, i came up with the proposal to create a web app
Issue
there are several reports that i dont want to recreate, they are just too complicated and i had already created these reports for the Desktop application i want to basically copy that report and paste it into the web application and link that in in the reportviewer and just change the datasource which would save me the trouble of recreating. i tried creating one of the report manual but the layout got messed up on the browser.
Plz help, thanks in advance
WinForms.ReportViewer can preview your rdlc using DisplayMode.PrintLayout but this is not possible with WebForms.ReportViewer where you basically always work with DisplayMode.Normal.
If exporting your web rdlc to PDF solves the layout problem, try display your report directly in this format.
I have windows application which consists of many forms.
Now I came across the situation where I want to make this application available online.
How to achieve such a result?
Actually that does not seem to be possible reason is that both domains are different and for different purposes. Browsers are developed to display HTML and not render windows forms. Secondly HTML will work in all OS even non windows.
Also even if you succeed in doing it it will work only on server and there is no way you can show windows form to the user via browser.
you might want to look into converting it to Silverlight 2.0 instead.
I have a customer requirement where they would like to have different windows of a web application on 2 different displays (monitors): data lookup and entry on one screen and a document viewer on the other. The document viewer will be Flash or Silverlight based and loaded in a webpage. The app will be at least partially based on SharePoint. There is a need for communication between the two windows: when for instance a new task is clicked in the "data" view, the accompanying document needs to be opened in the other one.
The difficulties as far as I can determine:
Opening the two windows from within a web app
Actively position the windows on the 2 displays
communication between the two windows
as robust a solution as possible from a user perspective (e.g., re-opening a closed window, tracking changes between them, etc.)
I am looking for pointers in getting this done. I understand that I can launch the second window from Javascript, but that does not give me a lot of control over it. This solution will run in a closed, controlled environment, so limiting the solution to a specific browser (preferably IE8+) or the need to install additional software/components is no problem.
If i were you i would implement this with silverlight and asp.net mvc.
create a state object which describes the state of the 2 windows, this can be consumed and updated by both the silverlight app via web services, and the mvc app via javascript, postbacks or web services.
We recently migrated a large ASP. website from framework 1.1 to framework 3.5 and in the process also migrated from a website to a web application.
On the surface everything seemed to work fine, but now we are discovering that none of the "pages" are doing what they used to.
The site is made up of one default.aspx page that loads all the "pages" as user controls. (I am guessing this was to achieve the same effect as having a master page before master pages were invented.)
I think we missed a trick (or twelve) during the migration. What are the big stumbling blocks that other people have experienced
Update
We managed to find the problem that was making our pages stop working, but can not figure out why: When we cleaned up the code of the main page, we added whitespace (a newline) between the open and closing tags of the control that all the other "page" user controls get loaded into. Once we removed the newline everything started working again. Can anyone explain this?
I have experienced problems during manual copying etc. that has lost the connection between the GUI controls and the event-methods in the code behind. There are differences between the different versions of ASP.NET on how the event handling is coupled, and there are even more than one way of doing it (automatic based on names or explicit in code), and this is easy to mess up when changing from one "standard" to another, which is what you do converting to a differen version of .NET. It is also an additional source of confusion for Visual Studio when you also converted from Web Site to Web Application.
I am guessing that the trick was just to do some editing in Visual Studio, and VS might have automagically re-attached event handlers etc.
One things you should know is that if your new server is 64 bit. There is a chance that the controls on the page will be loaded concurrently with the page. In a sense there will be a lot of timing issues. If you are not using 64 bit server however this is not relevant.