Friday, May 29, 2015

IE 8 to 11 migration and compatibility issues

Hey Guys,

Hope you guys are struggling a bit to overcome the compatibility issues after migrating from IE 8 to IE 11.

Solution is to modify the code as and where it needs to changes (css/javascript/etc). But we do have alternate solutions to continue with our development work and also for very critical applications for which they shouldn’t impact.

Solution-1: Add application/web site to compatibility list under "Compatibility View Settings" menu item. 

Solution-2: Enable "Enterprise Mode" under Tools menu.

Enterprise Mode, a compatibility mode that runs on Internet Explorer 11 on Windows 8.1 Update and Windows 7 devices, let's websites render using a modified browser configuration that’s designed to emulate Internet Explorer 8, avoiding the common compatibility problems associated with web apps written and tested on older versions of Internet Explorer.
Also we have a tool to add the applications list to work on Enterprise Mode – “Enterprise Mode Site List Manager”

Solution-3: Only for development purpose till we get a proper solution/mitigation plan on the changes to be done.

For versions of Internet Explorer 8 and above, this:
http-equiv="X-UA-Compatible" content="IE=9; IE=8; IE=7" />
Renders IE7 and IE8 as IE7, but IE9 as IE9. It allows for different levels of backwards compatibility. In real life, though, you should only chose one of the options:
 http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />
Adding "chrome=1" will allow the site to render in ChromeFrame for those users who have it, without affecting anyone else.
 http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" />

Hope it helps. Thank you. 

Tuesday, May 12, 2015

ASP.NET - Login failed for user 'DOMAIN\MACHINENAME$'

To avoid below error,
System.Data.SqlClient.SqlException: Login failed for user 'DOMAIN\MACHINENAME$'.

1. Try to prepare proper SQL connection string as

Initial Catalog=your_db_schema;
Integrated Security=False;
User ID=your_db_login; Password=??????" 

2. Remove Persist Security Info=True;

3. Other resolution:
In SQL Management Studio create an account for "DOMAIN\MACHINENAME" (do not browse for the account name, type it in manually) and then grant this account db_owner access to the SLAD database. After this, reinstall the product.