Embedding .Net and CSS

.NET is the way which deals with header management that deals with working themes, in the ASP .NET has a problem that is big that is the embedment’s of the styles sheets are at the bottom of the header list. If the user uses the master pages that has a header content section then the user is additional CSS or style tags to the header, the master page end up above the standard .css theme file, if the user tries to attempt to add any controls to the page the same thing will happen, whatever the user usages to add any controls to the page it ends up before the theme style sheet.A heavy CSS user is SharePoint it is both good and bad at the same time because it is hard coated in the site definitions and the best way to operate the changes in the site is CSS, 7 different style sheets are contained in a share point 2003 portal that will make up a total of 7403 lines of code and 1227 style sheet statements, but all these seven are not used hardly four are needed to be edited. When page is opened the style sheets will be pulled in order first one is OWS.css and next is MENU.css and the next is SPS.css.The very important thing to understand is the order that is used in style sheets since the last thing which is used in a declaration of the selector will be used on the current page, so if the user wishes to change anything the theme can be modified, when the theme is modified the settings which are contained in the style sheet will over ride the settings, the styles are for advanced users.