We use SQL Server 2012 and using version 44.17763.831.0 of Microsoft Edge. Edge, it would appear is supported for viewing reports but not for managing them. The screenshot below shows how in IE we are able to click on the drop down menu and edit a report, this does not work in Edge.
Does anyone know of a way around this or if the latest version of Edge now supports this? Or perhaps upgrading SQL server would help?
I had the same problem when I was using SQL SERVER 2008 with IE. So I downloaded the IE TAB extension to chrome and all SSRS features were working fine.
Go to Microsoft Edge Settings
Search for "Internet Explorer Compatibility"
Under "Internet Explore mode pages" add you SSRS pages address that need to be open under IE
All set.
That's it :)
Related
I have an HTML application that run offline, and I want to end up with a way to open the app from an exe file on Windows. I have tried Visual Studio, but the app does not run in the WebBrowser component.
I am pretty sure I have read that I can use Chrome (or some kind of Chrome version of Chrome) as a "bundled runtime", but I have a really hard time finding anything about it. Does it exist?
Using chrome as an engine (instead of "web views" based on Internet Explorer) would also make sure that the application would run nice on computers which has not updated Windows or browsers for a while.
You must be thinking of CEF: the Chromium Embedded Framework.
I am trying to open a SSRS report on Chrome. But due to some obscure reason it doesn't open up properly in Chrome. It shows up, but it shows up only in part of the whole webpage. It doesn't render to fit the whole webpage.However this does work fine with Firefox.
Details:
Chrome Version: Version 48.0.2564.103 (64-bit)
SSRS: 2008
OS: Mac OS X Yosemite 10.10.5
Below is the screenshot of it.
NOTE: This is not a duplicate issue. Since the report does show up. Unlike the other issues where it was not showing up at all.
Let me know if you need any more information.
Thanks in advance - Deb
Chrome has been notoriously difficult displaying SSRS reports for me.
Here are some suggestions/things you could try:
Check and make sure Javascript is enabled in Chrome
Install the IE Tab extension for Google Chrome
Make sure your chrome settings and environment meets requirements
Select list disable option is not working in firefox developer edition. Here is sample
fiddle
for select list disable option.I have check this fiddle in firefox standard edition and developer edition it is working in standard edition but not in developer edition.How to disable select list in firefox developer edition ?
Thanks
I have a .NET 3.5 website that we work on in Visual Studio 2010. The problem is that when we publish the website and put the files to the web server with IIS7, the display is different than what is shown when we run locally. The problem happens on all of our supported browsers: Chrome, IE, and Firefox. The control that is displaying incorrectly is an asp menu control. While I have read many other threads regarding issues with this control, none of the solutions seem right for my specific problem.
In chrome, I used the Firebug extension to compare the html and css for the desirable and undesirable displays. I found that the css is identical while the HTML is different. The information below compares the html tags that get generated for different browsers and publishing methods.
Visual Studio 2008 publish and local (desirable):
Chrome: ul, li
IE: ul, li
Visual Studio 2010 publish (undesirable):
Chrome: span
IE: table, tr, td
Our temporary workaround is very inconvenient. When we are ready to publish, we open the website in Visual Studio 2008 and publish from there.
Another problem I have that is related: sometimes, this menu is supposed to be hidden. When I publish from 2010, it is not hidden when it should be. Desirable behavior is achieved when running locally or publishing from Visual Studio 2008.
I saw the solution here that was the closest thing I found to my problem. ASP.NET Menu rendering different from vs2008 to vs2010 The only difference here is that the asker's problem was Chrome specific while my problem extends to all browsers. Maybe this solution can be tailored to my issue?
I haven't solved this problem exactly, but do think I found the problem. I read that there is a bug with visual studio where the app browsers dll gets published in .net 4.0 even though my project is .net 3.5. A workaround is to save the file from the 2008 publish and replace the file from the 2010 publish with the 2008 version. I guess this problem will go away once we upgrade our .net version.
So far I was using VWD 2010 express quite smoothly on Windows XP. Now I have got a new laptop - with Windows 7 64 bit. Yesterday I installed VWD 2010 express. I transfered all my data to the new laptop. When I open an existing project, it opened well and even runs very well. But when I am design mode I have lots of problems like
Cursor is not seen in the .aspx page and scrolling does not work. Cant edit anything. However .aspx.cs works normally
when I press Ctrl + F, Find window opens up but when I give find next, the instance is not seen and the page does not navigate to the instance
When I double click on a file in the solution explorer, i dont see it open. But when I minimise the entire VWD and maximise it, I see that the clicked page is open.
sometimes (mostly just after the project is loaded) part of the screen is black and when i minimise VWD and maximise, the page is properly shown.
I tried Repair and also uninstalled and reinstalled the entire VWD 2010 express - the problem still exists. I dont know what problem it could be. I did not encounter any problem while installing VWD. Could this be a VWD problem or memory problem (8GB RAM) or graphic card(dedicated) problem? Any help is highly appreciated.
I solved the issue yesterday, I logged in to the forum today to post my solution so that it helps someone later. Here is what I did:
I opened the "Compatibility Troubleshooter" in the control panel and identitified that there is a compatibility issue. So I made changes to open VWDexpress in the compatible mode (In my case it was Windows XP service pack2) and saved the settings. Now it works very well.