Problem (Bug) with IE7 Beta and VS2005 Build Style (CSS) Builder
For those running Visual Studio 2005 (VS2005) along side Internet Explorer 7 (IE7) Beta you may have noticed that the VS2005 CSS editor pops up then disappears immediately. You can reproduce by right click on a style in a CSS file and choose "Build Style". As with any Beta release challenges and compatibilities will arise. The product teams are aware of the issue and are working on it for the final release as indicated here:
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=257535&SiteID=1
As the information states you can workaround the issue by editing the registry (standard disclaimer for editing registry-backup machine, do with caution). There is a work around available for those willing to play with their registry:
- Open Registry Editor (Start/Run/RegEdit)
- Navigate to HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl
- Create a key if none exists for FEATURE_CSS_DATA_RESPECTS_XSS_ZONE_SETTING_KB912120
- Create a DWORD entry in HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_CSS_DATA_RESPECTS_XSS_ZONE_SETTING_KB912120
- Enter for name: devenv.exe
- It should automatically default to a value of 0 (otherwise change it)
- Shutdown all IE7 and VS2005 programs
- Start VS2005 and it should now work
I hope this helps ...
Comments
- Anonymous
June 25, 2006
I would just like to add to this..
This fix dose work, so long as you dont connect to the internet.
After you apply the fix, it works first time, then not after that..
Reboot, and it works all the time..
Connect to internet, and it the fix no longer works. - Anonymous
June 25, 2006
Ive just found out why..
Apparently in VS.NET, selecting the style builder on the html page on any element, or through the VS.NET menu is ok.
But clicking on style button in the properties panel fails, and stops it working all together.
Resart VS, and its ok again..
So dont open the style bulder from the properties panel and your ok. - Anonymous
August 29, 2006
I believe that this is fixed with the latest release of IE7 - well it works for me with no Registry changes! - Anonymous
October 04, 2006
Just to add to the last comment ... I am running on Vista (build 5472) with IE7 and the registry change is not needed. It appears the latest IE7 may include this fix (have not verified it on other OSes or Vista versions so mileage will vary).