I am using Report Viewer to remotely generate reports and I wish to have the print control button in the report header using IE 11.
This question is similar to the following:
Print button not available in ReportViewer using IE11
I have not been able to solve this issue. I have upgraded Report Viewer 2012 Runtime to 11.1.3452.0 and SQL Server 2008 R2 to SP2.
I am using Windows Server 2008 R2 and .NET framework 4.5.1 on the server. IIS is version 7.
I can see print buttons in all previous versions of IE (10,9,8,....)
I've also tried forcing the user agent to IE10 using this line:
meta http-equiv="X-UA-Compatible" content="IE=10"
According to the answers to the above question, I should have the print button. Any other suggestions besides compatibility mode or creating my own print button?
ReportViewer client printing feature relies on ActiveX which is not
supported by any browser except IE 9 (or earlier), that's why you do
not get print button when Chrome, Firefox or IE10/11 browser is
involved. For printing, you should export to PDF and let the user to
print it.
http://forums.asp.net/t/1962293.aspx?+Report+Viewer+print+Button+missing+from+browser
IE needs an add-on, RSClient, for the print button to work. Normally, the first time a user loads a report on IE, you'll see a prompt to download and install the add-on. Unfortunately, a lot of things can interfere with this. I'm not sure this will help you, but security settings were an issue for us.
Try this:
Remove the RSClientPrint add-on if it's installed. (Open the Control Panel, Internet Properties. Click the Programs tab and Manage Add-Ons.)
Click the Security tab, select the Trusted Sites zone, and then click the Sites button.
Add your web site to the zone and save your changes.
Open IE and navigate to your web site and the report. Hopefully, you'll see the prompt to download and install RSClientPrint and everything will work well. If it doesn't try to download, I would focus on the server.
Related
We have an Application Developed in ASP.NET inside which we have added an embedded Power Bi Dashboard using iFrame.
The Dashboard is working as expected in Chrome but facing the following issues with IE and Edge.
On IE the Dashboard is not being Displayed when viewed from the Embedded Application and upon clicking the power bi Sign-In button (shown within the Iframe), the application as a whole gets redirected to app.Powerbi.com/.... When you click the back button and refresh, still the sign-in prompt is shown in the iframe.
On Edge, the behavior is same as in IE, except that you click the back button from the app.powerbi.com website and then refresh the page, then the report renders correctly within the Iframe.
I tried clearing the Cache and Cookies, tried adding *.microsoft.com site and *app.powerbi.com to trusted sites list(per power bi forums) but still not working.
I suggest you check for the latest Windows updates and try to install it. Then after again try to test this issue on your side.
If the issue persists then hard refresh the page. Clear all the data for that site and again try to load the page.
I tested the issue with IE 11.1.18362.0 and Microsoft Edge 44.18362.1.0. As per my testing results, both browsers display the Power BI dashboard in ASP.NET site without any issue.
Output in IE 11:
Output in MS Edge:
If the issue persists then try to check the console to see whether there is any error or warning message. It can help to narrow down the issue.
I created a new VS 2013 project and viewed the default.aspx page with the Firefox browser. When I check the net calls it has made, I see it making constant calls to:
http://localhost:50682/6a663a78019845d5ade4a328cad09cc2/arterySignalR/poll?transport=longPolling&connectionToken=AQAAANCMnd8BFdERjHoAwE%2FCl%2BsBAAAAOBmDwPWa2ky2MAZXFHBMVAAAAAACAAAAAAAQZgAAAAEAACAAAADSADQXBVKiKczflJ0OzUjOLduFTJE4zd%2FLHWGpDfXnuAAAAAAOgAAAAAIAACAAAACyEX81VwilygfphPoEKCYQ6ZwrkzExoKfZzEMkqBKqqzAAAADG%2BDJbrEFOfsNm9OKhqacnGseQvrwy5kmyZnI5YJiZbjYFgzMELXHfwA7Sxjj4osJAAAAAvQvoG4N0nn8eB9FRaJaZyqaUDF%2F9ypvGN%2B%2BVefnx8U1Fq6P9HXO9vEC%2BfA2s8R4jik58rD4IcFMjM4P8l5kv6g%3D%3D&messageId=d-F1180A0E-W%2C0%7Cl%2C4%7Cm%2C0&requestUrl=http%3A%2F%2Flocalhost%3A50656%2Fdefaulttest&browserName=Firefox&tid=4&_=1384207744328
Why is it doing that?
How do I stop those calls?
I see an infinite number of calls made to the above URL every 6 seconds.
Please help me understand this and fix this.
This is working as intended. Artery aka BrowserLink is a real-time connection from Visual Studio to all browsers running your code. It essentially allows Visual Studio to interact with every browser.
For instance if you have IE, Opera, Chrome and Firefox all running your code and you're trying to ensure cross browser correctness; instead of going to each browser and hitting f5 to refresh you can just click the browser link refresh button which will auto-refresh all of the pages for you.
Not everyone wants or needs to have this functionality so if you do want to disable it, as Gustavo Armenta said you can disable it by following the steps here: How can I disable __vwd/js/artery in VS.NET 2013?
I would recommend you to read this post first Browser Link feature in Visual Studio Preview 2013 to understand about this new feature that comes in with VS 2013.
And then to disable this, simply uncheck the "Enable browser link" option.
You can hide the polling requests from the Chrome developer tools Network tab so that the requests you are actually interested in become visible. You can hide the polling requests by adding a negative filter:
On the Network tab, click the filter button to open the filter options
Enter "-poll" without the quotes to hide the polling requests.
Example:
Had issues with that on site running with KnockoutJS framework. Pages were freezing for 10 seconds until "BrowserLink" external scripts were loading (using Chrome browser).
Issue solved by disabling "Browser link" feature in VS 2013
Steps How to disable "Browser link" (thanks to Gustavo Armenta for leaving comment with link in question)
I've created a website using ASP.NET (C#) Framework 4.0
When running on my local IIS (in debug/release - before and after deployed) - the website is displayed correctly - as intended (checked on Internet Explorer 9, 10, Chrome and FireFox)
After I've deployed the website to my server (Windows Server 2008 DataCenter - Amazon hosting) - and only in IE 10 - the website is NOT displayed correctly - spacing is sometimes wrong, background colors sometimes disappeared, links not working properly, padding/margin is missing in some of the places and more... - it seems like the styles/CSS are partial... On other browsers (Chrome/FireFox/IE9) - it is displayed correctly (as intended)
I've tried to add the compatibility meta tags to IE=9 - didn't work (by the way, in IE10 - if I open the F12 tool - and change the Browser Mode to IE9 - it works!, but if I just change the Document Mode - it doesn't seem to help)
Why is Internet Explorer 10 evil??? Has anyone encountered this issue? any suggestions?
Thanks a lot! :)
As you write you are using F12 tools. My experience is that with Developer Tools running IE10 often does not apply all CSS rules (especially in at the end of external files). Refreshing the page or closing F12 tools usualy solves the problem. Also if you know which style is not applied it helps to disable and enable it again.
i have passe through a similar situation and some things just don't stay they way i want in every browser, so perhaps the better way out is to create CSS hacks tos specific spacing or styling issues you may have encoutered.
http://www.impressivewebs.com/ie10-css-hacks/
After a lot of searching and frustration, I've found the solution to my problem (here: http://www.nuget.org/packages/App_BrowsersUpdate)
Apparently the website should be updated to allow IE10 compatibility...
In your solution - install the ASP.NET Browser Capabilities Update using the following command in the "Package Manager Console" (can be started from "Tools"->"Library Package Manager" in your VS):
Install-Package App_BrowsersUpdate
(this will add ".browser" files to your website and few lines in your "web.config" file)
Rebuild and re-deploy your website and that's it! now my deployed website looks as intended on IE10!
(I still don't understand why it worked correctly on my localhost and not on the web server but at least the problem is solved)
Three fine browsers I have installed: the inimitable Mozilla, the traditional Internet Explorer, and the hot new Chrome. I love them all dearly, but when testing my ASP.NET application, I would prefer to do so using IE.
Please note, I've not deployed this application. I'm merely launching it from the Visual Studio project in which it was conceived. Would someone here be so good as to suggest a way in which I might specify the browser it launches in? Thank you.
Right-click on any .aspx page in Solution Explorer and choose Browse With...
You can then select Internet Explorer from the list and choose 'Set as Default' to make pages open with IE when you press F5.
Click and ASPX file in your solution explorer
Go > File > Browse with.. > Select IE then set it as your defautl browser.
Run your project.
i have to work on various web projects for different customers. some use IE only, some Firefox and other browsers in their companys.
i would like to debug project/solution A with IE and project/solution B with firefox (and so on) by just hitting F5 or "view in browser".
I do NOT want to switch the default browser in visual studio via:
right click on an .aspx file in the solution explorer
browse with...
selecting the browser i want to use
pressing "set as default" to make it remember my choise (optional)
everytime i have to work on another project/solution.
Can i save the default browser by solution or project and NOT via VS global settings somehow?
do you have any hint for me how to archive this? is there maybe even an addin for this?
thanks, toebens
In the project properties, in the Web section you can have it start an external application with parameters at the start of debug (F5) so you could specify the path of the browser as the Start External program path and the http://servername:port/virtualdirectory as the command line argument
alt text http://img142.imageshack.us/img142/3708/projectprops.gif