Asp.net question

[M_Lyons10]

Hi everyone. I don't mean to be a bother on here, but I have an Asp.Net application that I am trying to set up at 1&1. They sent me this link: http://faq.1and1.com/scripting_languages_supported/asp_net/8.html and said to save this file as default.asp and stick it in the root (Changing my domains and stuff).

I did this, but cam getting an error:

Active Server Pages error 'ASP 0129'

Unknown scripting language

/default.asp, line 1

The scripting language 'c#' is not found on the server.

I can't figure out what this issue means, so I wanted to ask if anyone happens to know.

Here are the contents of my default.asp which I did in Dreamweaver. I picked asp.net c#. I just cleared out the directories and domains. Am I missing something, I wasn't sure what the problem could be.

<script runat="server" Language="c#">
public void Page_Init(Object Src, EventArgs E)
{
	switch((Request.ServerVariables["HTTP_HOST"]).Replace("www.",""))
 	{
 		case "DOMAIN":
 			Response.Redirect("http://root/subdirectory/default.aspx");
 			break;
		case "DOMAIN":
 			Response.Redirect("http://root/subdirectory/default.aspx");
 			break;
		case "DOMAIN":
 			Response.Redirect("http://root/subdirectory/default.aspx");
 			break;
		case "DOMAIN":
 			Response.Redirect("http://root/subdirectory/default.aspx");
 			break;
		default:
			Response.Redirect("");
			break;
	}
}
</script>

Thanks everyone for your help. I really appreciate it. :)

[Antaris Veteran]

Hi,

There seems to be some confusion over the type of page you're supposed to be using. The page (default.asp) will (in its default configuration) map to the ASP (read: not ASP.NET) scripting engine, which supports Active Scripting Languages (the two most common being VBScript and JScript). Try renaming the file as default.aspx for it to map to the ASP.NET runtime.

[M_Lyons10]

Thank you very much for your response. I guess 1&1 support must have meant aspx... I just tried that, and I am now getting a different message, but it still isn't loading the page.

The error I am now getting is:

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>

<system.web>

<customErrors mode="Off"/>

</system.web>

</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>

<system.web>

<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>

</system.web>

</configuration>

I'm still trying to learn all of this, so it's a bit new to me. I did set up the subdirectory as an application in the 1&1 control panel (As the blog software's tutorial directed), but I can't do that with the root directory where this script is supposed to go, so 1&1 must automatically be able to know that it's an asp page. From the tutorial that 1&1 sent me (Which is here in case you're interested: http://faq.1and1.com.../asp_net/8.html ), it seemed like it was rather straight forward. I'm not really sure what I'm missing here (Though I'm guessing it's something silly).

Thanks Again for your help, I really appreciate it. :)

[Antaris Veteran]

That error denotes that an error has occured trying to process the request. By default, errors will only be shown on localhost, that being if the request originated from the same machine the application is running on. To view whatever the error is from a remote machine, you need to configure it to display the error. To do this, open (or create a file called) web.config.

If the file already exists, add the following in the <system.web ...> element:

<customErrors mode="Off" />

If the file does not exist, you can create a new one:

<?xml version="1.0" ?>
<configuration>
    <system.web>;
        <customErrors mode="Off" />
    </system.web>;
</configuration>

Once that file has been created, access the /default.aspx page again and let me know what the error is.

If you want me to have a closer look, you can PM me the files.