quote:Originally posted by dparsons
in your web.config change the Custom errors mode property to off. (In visual studio, double click the web.config and about 3/4ths of the way down the page you will see the custom errors property, flip it to off) This way you can tell us the actual error.
And no, the host machine of a web client does not need the runtime to run your apps.
Read this if you want to know how to get a correct reply for your question:
Technical Editor for: Professional Search Engine Optimization with ASP.NET
Why can't Programmers, program??
Thanks - I have done enough support that I was sure I knew that much about .NET.
Here is the actual error-
Object reference not set to an instance of an object.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
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.
[NullReferenceException: Object reference not set to an instance of an object.]
_Default.Page_Load(Object sender, EventArgs e) +39
System.Web.Util.CalliHelper.EventArgFunctionCaller (IntPtr fp, Object o, Object t, EventArgs e) +15
System.Web.Util.CalliEventHandlerDelegateProxy.Cal lback(Object sender, EventArgs e) +34
System.Web.UI.Control.OnLoad(EventArgs e) +99
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1061