Added: March/22/2007 at 1:22pm | IP Logged

I thought I had followed the instructions correctly.
When testing the testprotect.aspx, I am receiving the following error: 

Server Error in '/Secretdeal' Application.

---

Configuration Error

Line 56:       <compilation debug="false" explicit="true" />
Line 57: 
Line 58:       <authentication mode="Forms">
Line 59:         <forms name=".aspprotect~net" loginUrl="/aspprotect/aspplogin.aspx" protection="All" timeout="60" />
Line 60:       </authentication>

Added: March/22/2007 at 1:41pm | IP Logged

more or less you have to try different things until you get it working.. such is .NET

Added: March/22/2007 at 2:04pm | IP Logged

OK...

The site is hosted at godaddy.com with .NET 2.0.
The dll is .net 2.0 as well.

ASPProtect is installed in subdirectory /aspprotect.  This directory is where testprotect.aspx is located. 

Added: March/23/2007 at 10:28am | IP Logged

Then put in a request or call them??

Running ASP.NET scripts is a little more involved... it's not like classic ASP where any old host will do..

I mean if your doing anything serious with ASP.NET you either need to be running your own server or hosting with a serious hosting company that understands how to support ASP.NET.

GoDaddy is not one of those companies. They won't do jack sh*t for you when you ask, they usually don't understand what your asking for..  the interfaces they give you to control your website are horrible... etc etc etc
GoDaddy hosting is all about quantity not quality... they just want and have as many customers as they can handle. If your doing static files they are fine. Anything else and they suck.

If you plan to do a lot with ASP.NET I suggest you get a real hosting company like www.alentus.com or www.1and1.com

I mean there isn't anything I can do if web server settings can not be taken care of and adjusted. ASP.NET is a much more complicated animal.

You can try running the .NET authentication files from the root of your web site. If things are properally set up as far as .NET goes it should run. That means proper permissions set for the /bin folder as well as IIS application settings... etc etc etc

Really, most people have no problem getting the .NET authentication running, but then again you have to have some .NET troubleshooting experience and be running things on a server where settings can be adjusted and checked when necessary.

You also might want to think about trying to get the .NET authentication code running on a local development machine and really understanding IIS settings before you try to get it running on a hosts machine.