I have installed all the latest frameworks. Currently 4.5.1 with all rollups. Still there is no correct capability detection for IE 11.
It works fine for me to add my own capabiltiy detection configuration in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\Browsers and register a new factory dll using aspnet_regbrowsers.exe utillity.
...
The prefered way is however to activate application local browser detection using the App_Browsers ASP.NET folder. This is simply not working for me. No matter if I just launch my app from Visual Studio 2013 using IIS Express, or after publishing the site
(all ok, with app_browsers folder) to my local IIS 7 (i'm running on Windows 7 Pro x64 SP1. This way, for ex. the Request.Browser.Id returns "internetexplorer" and therefore also wrong capabilities.
Overall I could find very very litle details, explaining the inner workings of these teqniques in .NET Framework, ASP.NET and Visual Studio, to better grasp whats really going wrong. On some sites it states that IIS should autmatically pick up the contents
from App_Browsers folder if it exists. Ignoring any machine wide capability definition, that already exists in the app_browsers folder.
Also the app_browser.dll and __browserCapabilitiesCompiler.compiled is successfuly deployed to the site \Bin directory. I currently have undregistered the systemwide ASP.BrowserCapsFactory.dll using aspnet_regbrowsers -u.
According to your description above, I think we need look into this issue first.
I noticed that Internet Explorer 11 has a bug which prevents ASP.NET applications from running properly. Your users will view broken layout and JavaScript errors, which occurs due to a bug in the browser detection under .NET Framework 4.
In order to fix the above issue, you need to install
.NET Framework 4.5 on the server, which has built-in solution for this problem.
Please check whether you have the same issue above.
If you have any concern, please let me know.
Best regards
Angie
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
Hi I'm facing similar issue in Windows 2008 Server R2 .Net 4.5.1/IIS7. Local App_Browser in application or system wide app_browser files didn't help. Please suggest for a solution.
None
0 Points
4 Posts
Browser capabilities detection using local App_Browsers ASP.NET folder in ASP.NET project not wor...
Apr 09, 2014 02:04 AM|SWEDEV|LINK
Hi,
I have installed all the latest frameworks. Currently 4.5.1 with all rollups. Still there is no correct capability detection for IE 11.
It works fine for me to add my own capabiltiy detection configuration in C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Config\Browsers and register a new factory dll using aspnet_regbrowsers.exe utillity.
...
The prefered way is however to activate application local browser detection using the App_Browsers ASP.NET folder. This is simply not working for me. No matter if I just launch my app from Visual Studio 2013 using IIS Express, or after publishing the site (all ok, with app_browsers folder) to my local IIS 7 (i'm running on Windows 7 Pro x64 SP1. This way, for ex. the Request.Browser.Id returns "internetexplorer" and therefore also wrong capabilities.
Overall I could find very very litle details, explaining the inner workings of these teqniques in .NET Framework, ASP.NET and Visual Studio, to better grasp whats really going wrong. On some sites it states that IIS should autmatically pick up the contents from App_Browsers folder if it exists. Ignoring any machine wide capability definition, that already exists in the app_browsers folder.
None
0 Points
4 Posts
Re: Browser capabilities detection using local App_Browsers ASP.NET folder in ASP.NET project not...
Apr 09, 2014 02:05 AM|SWEDEV|LINK
Also the app_browser.dll and __browserCapabilitiesCompiler.compiled is successfuly deployed to the site \Bin directory. I currently have undregistered the systemwide ASP.BrowserCapsFactory.dll using aspnet_regbrowsers -u.
None
0 Points
4 Posts
Re: Browser capabilities detection using local App_Browsers ASP.NET folder in ASP.NET project not...
Apr 09, 2014 02:11 AM|SWEDEV|LINK
This is the ie11 definitions for my ie.browser file:
All-Star
32817 Points
3815 Posts
Re: Browser capabilities detection using local App_Browsers ASP.NET folder in ASP.NET project not...
Apr 13, 2014 10:36 PM|Angie xu - MSFT|LINK
Hi SWEDEV,
Welcome to asp.net forum.
According to your description above, I think we need look into this issue first.
I noticed that Internet Explorer 11 has a bug which prevents ASP.NET applications from running properly. Your users will view broken layout and JavaScript errors, which occurs due to a bug in the browser detection under .NET Framework 4.
In order to fix the above issue, you need to install .NET Framework 4.5 on the server, which has built-in solution for this problem.
Please check whether you have the same issue above.
If you have any concern, please let me know.
Best regards
Angie
Please remember to click "Mark as Answer" the responses that resolved your issue.
If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.
None
0 Points
4 Posts
Re: Browser capabilities detection using local App_Browsers ASP.NET folder in ASP.NET project not...
May 08, 2014 02:41 AM|SWEDEV|LINK
Hi,
I'm using .NET Framework 4.5.1. Is IIS Express supporting web_browsers folder detection from Visual Studio 2013?
A few weeks ago I also deployed it to IIS on my local machine, but that also did'nt work.
My web.config looks like this:
None
0 Points
1 Post
Re: Browser capabilities detection using local App_Browsers ASP.NET folder in ASP.NET project not...
Jun 16, 2017 05:02 PM|Bathri|LINK