asp vs. aspx Help!

Discussion in 'C, C++, C#' started by ivictus, Jan 9, 2011.

  1. ivictus

    ivictus Regular Member

    Jan 26, 2010
    Likes Received:
    I just acquired a site that is coded all aspx. it has c# which I cannot say I am comfortable with. I have seen it but really its Greek to me. I know PHP, + more but this, ???.

    Okay the big prob is that the index is set to redirect to a html subdirectory. I tried to just rewrite a index.asp or index.aspx but I get a 500 error.

    Is there a tut for this stuff? Why is asp giving me so much grief?

    Please, please help me asp Guru. You are my only hope.
  2. smack

    smack Junior Member

    Feb 1, 2010
    Likes Received:
    Software Engineer/Evil Genius
    inside .NET
    ok, a couple semantic distinctions to make. ASP is classic ASP. markup backed by unmanaged code usually in VBScript. ASP.NET is your markup (aspx) backed by managed code, generally in either VB.NET or C#. so redirecting to anything with an .asp extension isn't going to work to start with because you would be targeting aspx pages with a .NET web application.

    now, what kind of rewrite are you using? if you're hosting this in IIS then you should be able to set the default document on the applications property screen in IIS. a 500 error more or less means that the web server is seeing a malformed request that it doesn't want to process for whatever reason. so this is most likely being caused by whatever rewriting method you're trying to use.

    you are hosting this on a windows box, right? from what i understand there are ways to host .NET web applications on *NIX boxes, but they take some extra steps, and if i remember correctly, some middle tier software to make them jive.

    now one last question for you. how are you deploying this web app? there are certain situations where you can copy raw files (.aspx and .aspx.cs) directly to the server, but the usual deployment mechanism is to use the "Publish" or "Build" options under the "Build" menu in the Visual Studio IDE. you can either point it to the destination on the webserver, or publish it to a local folder then copy the comiled code (DLL's) and markup pages (.aspx) to the target folder on your web server.