After weeks of intensive study of MM.NET 3.5 doc and jump starts, I am starting project to create my login framework and test the methodology I plan to use for checking rights of each authenticated user for a form, or whatever resource designated. I am doing forms authentication but authenticating by a call to our Central Authentication System, then confirming the ticket issued by that authority and tracking the user in the asp.net session.

The above so you know I am still a newbie to mm.net and .NET, but on to the questions:

After creating a new mm.net web site from the mm.net web forms template, I have gone through and tried removing a couple of default items I will not be using, namely under admin the pages for security admin.

I made a copy of the default mmnet.css style sheet, and replaced the theme and stylesheet name with one of my choosing in the app_theme folder. Then I tracked down the references to the mmnet.css default style sheet and changed them. But at that point it occurred to me what if adding some mm.net object in future assumes the mmnet.css and them naming convention? Have I made a change I will regret? Did I err?

Also, I noticed that rebuilding the app produces no errors, but does produce seven warnings for each section in a web.config or an app.config file where you declare the connection values for the database to be referenced by the application or business objects. The apps/objects still work. But what is with the warnings, all of this type: "Message 1 Could not find schema information for the element 'databases'. C:\MM.NETJumpStart\StudathlBusinessObjects\StudathlBusinessObjects\app.config 55 3 StudathlBusinessObjects" and so on for basically every element and key in that section.

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