web.config contains assembly references that are automaticlly added. Why and how to solve?

I am sure that you came across the situation that while you work on a website and have multiple projects (that contain references to assemblies in the GAC) in the solution, when you compile for the first time you see many assemblies added to the web.config that you didn't add.

So you were probably asking your self why and tried to fixed it but failed.
Well after discussing this issue with few people in Microsoft that this is the behaviour - all the references of the project that are found in the GAC (including dependencies) will be added to the web.config - If you are asking me that i have no clue for the reason to do so.

Well guess what there is a workaround: If you go into the registry into HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Projects\{E24C65DC-7377-472B-9ABA-BC803B73C61A}\FilteredGACReferences, you will see a list of GAC references as keys that will not be copied into your web config if they are dependencies of references in your client project.
So the solution is easy just add the name of the assembly that you don't want to enter the web.config as a key.

There is another solution - to use the web deployment project and have a replacement section for Release.

Home you can use this information in your project.
Special thanks to John Dundon, Scott Guthrie.

DIV layout site - Ruthsarian Layouts

In the last couple of sayd i have been investigating the "Design" of a web application from the prepective of styling.
My main focus is on the TABLE VS. DIV issues, I found a very good site that shows DIV layout Ruthsarian Layouts

Enjoy.

Finding Security Compatibility Issues in Internet Explorer 7

Internet Explorer 7 (IE7) on Windows Vista, Windows XP Service Pack 2, and Windows 2003 Service Pack 1 will have many new security features which can cause compatibility issues for some Web applications and sites. Application compatibility logging in IE7 is designed to help IT professionals evaluate changes in behavior of Web applications and Web sites caused by the new security features in IE7 and test for compatibility when upgrading to IE7. Microsoft is planning to release an official toolkit to find compatibility issues and a pre-release version is expected during the second quarter of 2006. A temporary toolkit allows developers and IT professionals to begin testing application compatibility with IE7. When IE7's security features block content, this toolkit describes why the content was blocked. This toolkit is for temporary use only and will stop working when the pre-release toolkit is released, which is expected some time during the second quarter of 2006.
You can download it from "Finding Security Compatibility Issues in Internet Explorer 7"