Added: May/15/2006 at 10:47am | IP Logged

Hello,

I've installed the asp version and it works fine, and I've installed the asp.net add on and it seems to be working, as I was able to use the testprotect.aspx page successfully.  Now that I have added the include for aspx I am getting the following error from the server (XP Pro).

Compilation Error

Description: An error occurred during the compilation of a resource required to service this request. Please review the following specific error details and modify your source code appropriately.

Compiler Error Message: BC30689: Statement cannot appear outside of a method body.

Source Error:

Line 15: <% Line 16: ' This is part of the too many login attempts lockdown code which sets a cookie to block login attempts for a certain amount of time Line 17: If LoginLockDown Then Line 18: If Request.Cookies("PASSWORDSYSTEMCOOKIETRIAL")("LoginTries") <> "" Then Line 19: If Cint(Request.Cookies("PASSWORDSYSTEMCOOKIETRIAL")("LoginTrie s")) = Cint(LoginLockDownAttempts) Then

Source File: c:\inetpub\wwwroot\check_user_inc.asp    Line: 17

Please let me know if you have any ideas.  I am using Vis Web Dev 2005.  In the IDE I have 110 errors on my default.aspx, all pointing to the last line of <script> where the includes are.  The problem seems to be in the check_user_inc.asp. 

Please let me know if you need more info.

I also seem to be missing a file called

Charlie

Added: June/16/2006 at 10:51am | IP Logged

1st off, I am sorry I didnt answer any of your posts until now. For some reason I just never saw them or got an email about then, not sure why.

----------------------------

Because you cant use the classic asp include file with ASP.NET pages.
Of course your gonna get errors all over the place.

Classic ASP and ASP.NET are two very seperate technologies.

You can only protect ASP.NET pages using the ASP.NET Authentication Add-on that I sell.

Also, your not missing "aspplogin.aspx.vb" that is not a file you get as it is contained in the Authentication DLL which we do not give the source code for. When that page references that file it is really taking it from the dll. That is how code.behind works in .NET.

You need to protect the ASP.NET pages the way we tell you to. Forget what you do with the classic ASP pages. It's totally different.