Semut's References

I am sure anyone who have developed/run web application project before know how crucial the application compatible with the mainstream browser in the market. If you search in the google and look for the most rant about browser. It would be no surprise that IE is on top of the list. Ok. this is not a IE bash thread and never intended to be. Because the relation of IE to the development team or business is actually a love and hate sentiment. Why? thanks to IE, development team can focus only compatibility test on IE and ensure if it works there. The rest (not mainstream browser) on the other hand can be ignored (unfortunately, that would mean sayonara to my favorite Mozilla Firefox). To cut the story short, let just explain based on my experience (it could vary on your experience, just my exposure) why people would rant about IE. They said, it is bad, but how bad is bad? Most people would start off "trying" to make the application at least compatible with IE6. Because the older

This is something that definitely continuous integration able to identify. Something to do with ASP.NET web page running well in development but not in the live environment or pre-screen - continuous integration environment. Server Error in '/' Application. -------------------------------------------------------------------------------- Parser Error Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately. Parser Error Message: The file '/XXX/XXXX.aspx.cs' does not exist. Source Error: Line 1: Line 2: <%@ Page Language="C#" AutoEventWireup="true" CodeFile=" For seasoned developers, if they have started development since .NET 1.1. This is something definitely they familiar with. Because, in the past, all this are not so automated in older version of Visual Studio.NET.So, in this case, it is the CodeFil