Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Web Development
  3. ASP.NET
  4. aspx 2.0 deployment and class object

aspx 2.0 deployment and class object

Scheduled Pinned Locked Moved ASP.NET
sysadmincsharpasp-nethostinghelp
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • H Offline
    H Offline
    Haseeb Mukhtar
    wrote on last edited by
    #1

    Hello all. I am working on asp.net 2005, the solution is wroking fine in local machine but when I copied pages in web hosting server its giving some exception, i was not ably to see the exact exception because in webserver its send to specific page if found any error. I removed the line where I was creating object of other class and then copied to web and it works fine. So is there is any specific way for creating object of other class in aspx 2005.

    G 1 Reply Last reply
    0
    • H Haseeb Mukhtar

      Hello all. I am working on asp.net 2005, the solution is wroking fine in local machine but when I copied pages in web hosting server its giving some exception, i was not ably to see the exact exception because in webserver its send to specific page if found any error. I removed the line where I was creating object of other class and then copied to web and it works fine. So is there is any specific way for creating object of other class in aspx 2005.

      G Offline
      G Offline
      Grapes R Fun
      wrote on last edited by
      #2

      Something as simple as creating an object should not cause problems! In order to properly troubleshoot this, you have to see the exception... in your web.config change your custom error tag to the following: You may have other elements/attributes associated with your customErrors, but you should be able to get the idea. Now, you should be able to see the actual exception ONLY when you access the application from the hosting server. Also, check your event viewer to see if asp.net has logged any application errors/warnings. I got a couple of questions, did you precompile your web project? Did you send over the Website, or the whole solution?

      Nila "...for that, I will need a large cup of coffee and a brand muffin!" -Samantha Bea

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups