[ad_1]
\n<\/p>\n
Adding<\/p>\n
<authorization>\n<\/code><\/pre>\ntag with the code shown in above question would make any anonymous user from accessing any page other than Login, as each request will be redirected to LogIn Page with no other content allowed from server including basic CSS<\/strong>. <\/p>\n<\/li>\n- \n
Suggested solution 1 on the web was to add <\/p>\n
<location> \n<\/code><\/pre>\ntag which works for css but causes issue with the System.Linq. <\/p>\n<\/li>\n<\/ol>\n
Here is the solution for the StUpIdItY. First of since nothing was working I saved web.config contents and deleted web.config and recreated from scratch as follows. <\/p>\n
Step1<\/h1>\n <?xml version=\"1.0\"?>\n <configuration>\n<system.web >\n <compilation debug=\"true\" targetFramework=\"4.0\"\/>\n <authentication mode=\"Forms\" >\n <forms loginUrl=\"~\/Login\/frmLogin.aspx\" \/>\n <\/authentication>\n <authorization >\n <deny users=\"?\" \/>\n <\/authorization>\n<\/system.web>\n<\/code><\/pre>\n<\/p>\nThis first step took Linq errors away. <\/p>\n
Step 2<\/h1>\n
Problem with this approach is since I am using external CSS file it will not apply to LOGIN page as <\/p>\n
<authorization >\n <deny users=\"?\" \/>\n <\/authorization>\n<\/code><\/pre>\nwill block any anon user.
\nYou can still use CSS by having css in separate folder and adding another web.config file under the folder where your external CSS is. In my case my css file was, StyleSheet.css under Styles folder. So I just added web.config there as follows. <\/p>\n
<?xml version=\"1.0\"?>\n<configuration>\n<system.web>\n <authorization>\n <allow users=\"*\"\/>\n <\/authorization>\n<\/system.web>\n<\/configuration>\n<\/code><\/pre>\nNow my css is working fine, as well as I can use LogIn page and Linq. <\/p>\n
Thanks to MICROSOFT for wasting my time on these issues but I hope I can save frustrations to many in the future. <\/p>\n<\/p><\/div>\n