Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 4 of 4
  1. #1
    New to the CF scene
    Join Date
    Dec 2011
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    ASP.NET C# Publish Help

    Where I work we got a new job. Its maintenance of a website:http://www.c-ibo.org

    The previous programmer left the customer and us out in the cold, he wont return our calls. I'm a mac user with basic HTML & CSS Skills, nothing like ASP.NET C#.

    I need to make small changes in the meantime, while the customer looks for a more competent programmer with ASP.NET C# experience.

    I borrowed a PC with Visual Studio 2010. I got to add a new page. Right click on the folder on the project, theat i need to add a new page to, with the codebehind .cs file seperate, preview the page, looks fine, hit build, then publish to file, the upload via ftp. The new page wont load this is what I get after clicking the link:http://www.c-ibo.org/Error.htm?aspxe...IBSchools.aspx the correct filepath should be http://www.c-ibo.org/Information/Art...IBSchools.aspx

    Any quick ideas on what I'm doing wrong, and what I can do to resolve this, would be great, like I said I told the customer we can't do it, but we need to at least get a few things updated and changed while they look for a programmer with ASP.NET C# experience.

  • #2
    Regular Coder
    Join Date
    Apr 2009
    Posts
    244
    Thanks
    1
    Thanked 20 Times in 20 Posts
    Hey jmk1788,

    No way to tell exactly what them problem is based on what you provided. It looks like it's set to redirect to a custom error page Error.htm whenever some run-time error occurs. To verify this, look inside the Web.config file and find section named "customErrors". In any case, here's some advice:

    1. Create a test environment where you can test your changes prior to putting them on a live site.
    2. In this test environmment, turn off the custom error handling inside Web.config
    3. In the new page you're trying to deploy, add property Debug="true" into the Page directive. So, it will look something like <% Page Language="C#" Debug="true" .... %>. At this point, when you hit the page, you should see all the error details.
    4. I always say, in this situation, just start simple: Remove/comment out all the C# codebehind. Test just the aspx page. When that's working, just start adding the codebehind little bits and pieces at a time. This will help you identify what the problem is, if it's not so clear when looking at the error details mentioned in previous step.

    Regards,
    Mike

  • #3
    Senior Coder alykins's Avatar
    Join Date
    Apr 2011
    Posts
    1,722
    Thanks
    41
    Thanked 191 Times in 190 Posts
    just an additional "fyi"
    I agree commenting out everything and "getting it to work" on a basic level is a good idea, but make sure you leave the functions... if you comment out for example
    Code:
    btn_Example_Click(object sender, EventsAgrs e){...
    and then you have a button that calls that you will error out- may end up spending hours chasing a problem you created by commenting things out

    I code C hash-tag .Net
    Reference: W3C W3CWiki .Net Lib
    Validate: html CSS
    Debug: Chrome FireFox IE

  • #4
    Regular Coder
    Join Date
    Apr 2009
    Posts
    244
    Thanks
    1
    Thanked 20 Times in 20 Posts
    Yes, absolutely. When I said "comment out all the codebehind", I meant only the code inside the methods. Sorry about that.


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •