>Hi Ron,
>
>The mm.css file isn't on anything but is included as a starter css file you can use and is used with the jump starts for web. You should be free to create your own, extend that one or delete it as you wish. Then when you have what you want, just drag it onto the aspx page in the head section or in your master page if you are using one.
>
>As to the warnings, you would have to post some of the app.config or web.config file that is being referenced for me to know what that is about.
>Tim
>

By the way, re: the css file, what I did was just make a copy of the mmnet.css file, and left all id and elements intact. I was concerned that some towards the bottom looked like they might be used by mm.net controls or other aspects of the framework. I then just edited to change some colors, and how some of the code was written, e.g. many of the uses of keywords for color cause warning messages when the project is built in Visual Studio, so I tweaked till I got rid of all of those. And I prefer using the #NNNNNN syntax for colors rather than keywords, stuff like that. At that point, the plan was to then expand the style sheet as needed, or tweak colors or elements affecting appearance.

As for the code in the web.config / app.config file triggering the warning messages, here it is. It is in the position as originally entered when a project is created, at the bottom right before the final close configuration tag.

	<databases>
        <add key="Studathl\Connection" value="server=(local);Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Studathl" />
        <add key="Studathl\DataAccessClass" value="DataAccessSql" />
	</databases>
	<system.windows.forms jitDebugging="true" />

Also, as a thought experiment, I just created a fresh, new, untouched default setup of an mm.net web site using the mm.net web forms template, so I would have a copy on the file system to reference. The warnings are there in the virgin default setup. There are seven of them, all related to the databases element in the config file.

Message	1	Could not find schema information for the element 'databases'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	176	4
	C:\BegASPNET\DefaultMMNETWebSiteSetup\

Message	2	Could not find schema information for the element 'add'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	177	6	
    C:\BegASPNET\DefaultMMNETWebSiteSetup\

Message	3	Could not find schema information for the attribute 'key'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	177	10	
    C:\BegASPNET\DefaultMMNETWebSiteSetup\

Message	4	Could not find schema information for the attribute 'value'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	177	37	
    C:\BegASPNET\DefaultMMNETWebSiteSetup\

Message	5	Could not find schema information for the element 'add'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	178	6	
    C:\BegASPNET\DefaultMMNETWebSiteSetup\

Message	6	Could not find schema information for the attribute 'key'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	178	10	
    C:\BegASPNET\DefaultMMNETWebSiteSetup\

Message	7	Could not find schema information for the attribute 'value'.	C:\BegASPNET\DefaultMMNETWebSiteSetup\Web.Config	178	42	
    C:\BegASPNET\DefaultMMNETWebSiteSetup\

Ronald D. Edge
Director of Information Services
Indiana University Athletics
http://iuhoosiers.com
edge@indiana.edu