- Solution (sln) file.
- Solution user Options (.suo) file.
- Project configuration file (.vbproj) or .vcproj file
- .aspx, .asmx, .ascx
- .aspx.vb or .aspx.cs - code behind fiels
- globax.asax
- resouce file .resx
- other files .txt, .rpt
- style .css files
- congig file web.config.
- discovery file .disco or .vbdisco
- Project Assembly files (.dll)—All of the code-behind files (.aspx.vb and .aspx.cs) in a project are compiled into a single assembly file that is stored as ProjectName.dll. This project assembly file is placed in the /bin directory of the Web application.
- AssemblyInfo.vb or AssemblyInfo.vb or AssemblyInfo.cs—The AssemblyInfo file is used to write the general information, specifically assembly version and assembly attributes, about the assembly.
HTML5 has introduced lots of new cool tags . Not all the browsers support all tags and also the implementation of these tags may be different for each browser. HTML5 specification defines the functional aspects of these tags and not the implementation. Also the general concensus is that by 2022 all browsers will support all new features of HTML5. Of all the modern browsers, Chrome seems to have implemented most, if not all, featutes of HTML5. IE9 supports few. Firefox sits in between. So as a developer how do you make use of the cool HTML5 features without causing any compatibility issues with existing browsers? Traditionally developers have used User Agent to detect browser type and use the features accordingly. However these days, you can easily change a User Agent by using addons in your browser. So you need a more robust way to detect the features supported by the browser as the same engine of two different versions of a browser mig...
Comments