I'm uploading a project to a remote server and its not working for some
reason, but I dont know how to start debugging as it works on my machine?

The only thing I think it could be is that I've set the database up wrongly
in the remote server but a) it looks OK, and b) I dont know how to test this
theory.

Any ideas on how and where to start as the refernces to lines in code below
dont help me much really

Any help would be much appreciated :)

The error I get is:

Exception Details: System.NullReferenceException: Object reference not set
to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web
request. Information regarding the origin and location of the exception can
be identified using the exception stack trace below.

Stack Trace:


[NullReferenceException: Object reference not set to an instance of an
object.]
HousingCare.Templates.PageTemplate.LoadControls() in
c:\inetpub\wwwroot\housingcare\components\pagetemplate.cs:109
HousingCare.Templates.PageTemplate.OnInit(EventArgs e) in
c:\inetpub\wwwroot\housingcare\components\pagetemplate.cs:98
HousingCare.Pages.HomePage.OnInit(EventArgs e) in
c:\inetpub\wwwroot\housingcare\index.aspx.cs:54
System.Web.UI.Control.InitRecursive(Control namingContainer) +234
System.Web.UI.Page.ProcessRequestMain() +171

John Dillon

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.380 / Virus Database: 213 - Release Date: 24/07/2002

John Dillon wrote:
> I'm uploading a project to a remote server and its not working for
> some reason, but I don't know how to start debugging as it works on my
> machine? 
> 
> The only thing I think it could be is that I've set the database up
> wrongly in the remote server but a) it looks OK, and b) I don't know
> how to test this theory.
> 
> Any ideas on how and where to start as the references to lines in code
> below don't help me much really

I suggest:
1)  If you are not publishing to your own staging site (different from
your development site) do that first.
2)  If you haven't got exception logging put some in.  You can append to
a file.  You can also get more than the standard exception page you're
showing into that file.
3)  After 2 above work damn hard to prevent these messages showing to
your customers.  Try...catch etc.
4)  We can't help without source code!
5)  Think about putting in test pages that do things like signal your
connections are working.

Being able to debug your code locally and remote is fundamental.  You
MUST master it, you have no choice if you are a serious player. 

Mike Gale, Decision Engineering (NZ) Ltd.

CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee/s. 

If you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction of
this message is prohibited without prior written consent.  Any views
expressed in this message may not reflect the views of Decision
Engineering.    

Mike

Got it sorted thanks... more through luck than anything else I suspect. I
must say the debugging side of things has been one of the most difficult
things to pick up about ASP.NET. I have been avoiding logging to files etc
but think I'll follow your steps as a guide from someone who clearly knows
better.
Thanks

-----Original Message-----
From: Mike Gale [mailto:info@d...]
Sent: 18 November 2002 19:50
To: Website Programming with ASP.NET
Subject: [aspdotnet_website_programming] RE: Not working on remote
server?


John Dillon wrote:
> I'm uploading a project to a remote server and its not working for
> some reason, but I don't know how to start debugging as it works on my
> machine?
>
> The only thing I think it could be is that I've set the database up
> wrongly in the remote server but a) it looks OK, and b) I don't know
> how to test this theory.
>
> Any ideas on how and where to start as the references to lines in code
> below don't help me much really

I suggest:
1)  If you are not publishing to your own staging site (different from
your development site) do that first.
2)  If you haven't got exception logging put some in.  You can append to
a file.  You can also get more than the standard exception page you're
showing into that file.
3)  After 2 above work damn hard to prevent these messages showing to
your customers.  Try...catch etc.
4)  We can't help without source code!
5)  Think about putting in test pages that do things like signal your
connections are working.

Being able to debug your code locally and remote is fundamental.  You
MUST master it, you have no choice if you are a serious player.

Mike Gale, Decision Engineering (NZ) Ltd.

CAUTION - This message may contain privileged and confidential
information intended only for the use of the addressee/s.

If you are not the intended recipient of this message you are hereby
notified that any use, dissemination, distribution or reproduction of
this message is prohibited without prior written consent.  Any views
expressed in this message may not reflect the views of Decision
Engineering.





---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.380 / Virus Database: 213 - Release Date: 24/07/2002

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.380 / Virus Database: 213 - Release Date: 24/07/2002