asp.net not working on stoli

Status
Not open for further replies.

lhyman

New Member
Messages
198
Reaction score
0
Points
0
Maybe I am doing something wrong...

a simple page from w3 schools

http://www.w3schools.com/aspnet/aspnet_controls.asp

w3 schools result:

http://www.w3schools.com/aspnet/valipage.aspx

my page:

http://hal.pcriot.com/test1.aspx

the code:

Code:
<html>
<body>
<form runat="server">
<p>Enter a number from 1 to 100:
</p>
<asp:TextBox id="tbox1" runat="server" />
<p>
<br /><br />
</p>
<asp:Button Text="Submit" runat="server" />
<p>
<asp:RangeValidator
ControlToValidate="tbox1"
MinimumValue="1"
MaximumValue="100"
Type="Integer"
Text="The value must be from 1 to 100!"
runat="server" />
</p>
</form>
</body>
</html>

My result: (after hitting refresh)

Code:
[B]Server Error in '/' Application[/B]

[B]Description:[/B] 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.
[B]Details:[/B] 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>

[B]Notes:[/B] 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>
[B]Version information: [/B]Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433 <!--

Is this because of a limitation with Mono, or is asp.net not really working?

Thanks
 
Last edited:
Status
Not open for further replies.
Top