Good point. My Site.Master also has a menu (Bootstrap 3) which I don't think needs the Form. I found a couple of threads on Stackoverflow dealing with the exactly the same issue I have. But in their case(s) they actually - I think - have a log in form within Site.Master. In my case, my login form is a Content form. Reading company name from web.config should not present a big overhead though.
Thank you!
>In theory, yes. But...as with anything in software, it depends. For example, you'll have to pull the company name from the web.config instead of relying on it being sent over the postback. There may be other things you have to tweak.
>
>>You make it too simple <g>. Do I understand you correctly that I can safely remove the Form from the Site.Master and use it (Form element) in the Content pages where I need it?
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
