System.Web.HttpContext

[Rob Morgan]

For some reason I can't pass the Context to my remoting object. When I run
this the application just shows the thrown exception, it never sends the
Context it to the remoting server. If I only send the exception it works.
Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )
ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter
prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Marina]

Remoting an HttpContext is kind of like trying to remote a SQL connection -
how could it possibly work? The HttpContext holds a live connection to the
response stream as well as to the request stream - you can't
serialize/deserialize something like that.

"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...

For some reason I can't pass the Context to my remoting object. When I run
this the application just shows the thrown exception, it never sends the
Context it to the remoting server. If I only send the exception it works.
Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )
ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Girish Bharadwaj]

I have never done this before. Anyway: I dont think HttpContext is
serializable. You can probably try sending the HttpContext.Current.Request
if you just want to get the current request.

--
Girish Bharadwaj
http://msmvps.com/gbvb
"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...

For some reason I can't pass the Context to my remoting object. When I run
this the application just shows the thrown exception, it never sends the
Context it to the remoting server. If I only send the exception it works.
Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )
ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Girish Bharadwaj]

Ignore my last reply. HttpRequest is not serializable too. :(

--
Girish Bharadwaj
http://msmvps.com/gbvb
"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...

For some reason I can't pass the Context to my remoting object. When I run
this the application just shows the thrown exception, it never sends the
Context it to the remoting server. If I only send the exception it works.
Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )
ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Patrice]

Tell us perhaps more about what you need in this. I would pass only the
necessarty info as - as noted by Marina - it would be similar to remoting a
connection.

Perhaps could you use a web service ? What are you trying to achieve ?

Patrice

--

"Marina" <so*****@nospam.com> a écrit dans le message de
news:e1**************@TK2MSFTNGP11.phx.gbl...

Remoting an HttpContext is kind of like trying to remote a SQL connection - how could it possibly work? The HttpContext holds a live connection to the response stream as well as to the request stream - you can't
serialize/deserialize something like that.

"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...

For some reason I can't pass the Context to my remoting object. When I run this the application just shows the thrown exception, it never sends the
Context it to the remoting server. If I only send the exception it works. Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter

prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Rob Morgan]

Make perfect sense, thanks

"Marina" <so*****@nospam.com> wrote in message
news:e1**************@TK2MSFTNGP11.phx.gbl...

Remoting an HttpContext is kind of like trying to remote a SQL connection - how could it possibly work? The HttpContext holds a live connection to the response stream as well as to the request stream - you can't
serialize/deserialize something like that.

"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...

For some reason I can't pass the Context to my remoting object. When I run this the application just shows the thrown exception, it never sends the
Context it to the remoting server. If I only send the exception it works. Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter

prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Rob Morgan]

I've made a remoting exception handler and I want applications to send it
enough information so we can route/track down the errors. I've got it
accepting Server.GetLastError().InnerException, and I wanted to include the
context information. Looks like I'm going to have to send it the Response,
Request, and Enviroment objects if that's possible. The smaller amount of
code that the applications have to use the better.

Thanks

"Patrice" <no****@nowhere.com> wrote in message
news:OS**************@TK2MSFTNGP12.phx.gbl...

Tell us perhaps more about what you need in this. I would pass only the
necessarty info as - as noted by Marina - it would be similar to remoting a connection.

Perhaps could you use a web service ? What are you trying to achieve ?

Patrice

--

"Marina" <so*****@nospam.com> a écrit dans le message de
news:e1**************@TK2MSFTNGP11.phx.gbl...

Remoting an HttpContext is kind of like trying to remote a SQL

connection -

how could it possibly work? The HttpContext holds a live connection to

the

response stream as well as to the request stream - you can't
serialize/deserialize something like that.

"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...

For some reason I can't pass the Context to my remoting object. When I run this the application just shows the thrown exception, it never sends the Context it to the remoting server. If I only send the exception it works. Any ideas appreciated

protected void Application_Error(Object sender, EventArgs e)
{
ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
(ODE.Enterprise.Exception.Common.IExceptionHandler )

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter

prise.Exception.Common.IExceptionHandler));
exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
System.Web.HttpContext.Current);
}

[Patrice]

Humm.. And what is the reason behind remoting the exception handler ? What
do you do with the information once you handler retrieved it ? If this is to
produce a trace message, you could perhaps produce the trace message and
sends directly this information to the handler rather than to send this and
create the trace message at the other end.

Also what benefit are you trying to reach by remoting the handler ?

Patrice

--

"Rob Morgan" <ro********@ode.state.oh.us> a écrit dans le message de
news:O$*************@TK2MSFTNGP15.phx.gbl...

I've made a remoting exception handler and I want applications to send it
enough information so we can route/track down the errors. I've got it
accepting Server.GetLastError().InnerException, and I wanted to include the context information. Looks like I'm going to have to send it the Response,
Request, and Enviroment objects if that's possible. The smaller amount of
code that the applications have to use the better.

Thanks

"Patrice" <no****@nowhere.com> wrote in message
news:OS**************@TK2MSFTNGP12.phx.gbl...

Tell us perhaps more about what you need in this. I would pass only the
necessarty info as - as noted by Marina - it would be similar to remoting

a

connection.

Perhaps could you use a web service ? What are you trying to achieve ?

Patrice

--

"Marina" <so*****@nospam.com> a écrit dans le message de
news:e1**************@TK2MSFTNGP11.phx.gbl...

Remoting an HttpContext is kind of like trying to remote a SQL

connection -

how could it possibly work? The HttpContext holds a live connection to

the

response stream as well as to the request stream - you can't
serialize/deserialize something like that.

"Rob Morgan" <ro********@ode.state.oh.us> wrote in message
news:O9**************@TK2MSFTNGP11.phx.gbl...
> For some reason I can't pass the Context to my remoting object. When

I run

> this the application just shows the thrown exception, it never sends

the > Context it to the remoting server. If I only send the exception it

works.

> Any ideas appreciated
>
> protected void Application_Error(Object sender, EventArgs e)
> {
> ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler =
> (ODE.Enterprise.Exception.Common.IExceptionHandler )
>

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter > prise.Exception.Common.IExceptionHandler));
> exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
> System.Web.HttpContext.Current);
> }
>
>

[Rob Morgan]

We will probably email it to our admins, or write it out to file, or
database it. I think your right, produce the trace message then send it.
What would be the best way to accomplish this?

"Patrice" <no****@nowhere.com> wrote in message
news:#b*************@TK2MSFTNGP09.phx.gbl...

Humm.. And what is the reason behind remoting the exception handler ? What
do you do with the information once you handler retrieved it ? If this is to produce a trace message, you could perhaps produce the trace message and
sends directly this information to the handler rather than to send this and create the trace message at the other end.

Also what benefit are you trying to reach by remoting the handler ?

Patrice

--

"Rob Morgan" <ro********@ode.state.oh.us> a écrit dans le message de
news:O$*************@TK2MSFTNGP15.phx.gbl...

I've made a remoting exception handler and I want applications to send it

enough information so we can route/track down the errors. I've got it
accepting Server.GetLastError().InnerException, and I wanted to include the

context information. Looks like I'm going to have to send it the Response, Request, and Enviroment objects if that's possible. The smaller amount of code that the applications have to use the better.

Thanks

"Patrice" <no****@nowhere.com> wrote in message
news:OS**************@TK2MSFTNGP12.phx.gbl...

Tell us perhaps more about what you need in this. I would pass only the necessarty info as - as noted by Marina - it would be similar to remoting

a

connection.

Perhaps could you use a web service ? What are you trying to achieve ?

Patrice

--

"Marina" <so*****@nospam.com> a écrit dans le message de
news:e1**************@TK2MSFTNGP11.phx.gbl...
> Remoting an HttpContext is kind of like trying to remote a SQL
connection -
> how could it possibly work? The HttpContext holds a live connection

to the
> response stream as well as to the request stream - you can't
> serialize/deserialize something like that.
>
> "Rob Morgan" <ro********@ode.state.oh.us> wrote in message
> news:O9**************@TK2MSFTNGP11.phx.gbl...
> > For some reason I can't pass the Context to my remoting object. When I

run
> > this the application just shows the thrown exception, it never

sends the

> > Context it to the remoting server. If I only send the exception

it works.
> > Any ideas appreciated
> >
> > protected void Application_Error(Object sender, EventArgs e)
> > {
> > ODE.Enterprise.Exception.Common.IExceptionHandler exceptionHandler = > > (ODE.Enterprise.Exception.Common.IExceptionHandler )
> >
>

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter

> > prise.Exception.Common.IExceptionHandler));
> > exceptionHandler.RaiseError(Server.GetLastError(). InnerException,
> > System.Web.HttpContext.Current);
> > }
> >
> >
>
>

[Patrice]

Just call your hanlder from the Application_Error event (available in
global.asax).

IMO there is no need to remote this. Just have the local handler create a
message and send it to the support team....

Patrice
--

"Rob Morgan" <ro********@ode.state.oh.us> a écrit dans le message de
news:OR**************@TK2MSFTNGP14.phx.gbl...

We will probably email it to our admins, or write it out to file, or
database it. I think your right, produce the trace message then send it.
What would be the best way to accomplish this?

"Patrice" <no****@nowhere.com> wrote in message
news:#b*************@TK2MSFTNGP09.phx.gbl...

Humm.. And what is the reason behind remoting the exception handler ? What

do you do with the information once you handler retrieved it ? If this is

to

produce a trace message, you could perhaps produce the trace message and
sends directly this information to the handler rather than to send this and

create the trace message at the other end.

Also what benefit are you trying to reach by remoting the handler ?

Patrice

--

"Rob Morgan" <ro********@ode.state.oh.us> a écrit dans le message de
news:O$*************@TK2MSFTNGP15.phx.gbl...

I've made a remoting exception handler and I want applications to send

it enough information so we can route/track down the errors. I've got it
accepting Server.GetLastError().InnerException, and I wanted to include the

context information. Looks like I'm going to have to send it the Response, Request, and Enviroment objects if that's possible. The smaller amount of code that the applications have to use the better.

Thanks

"Patrice" <no****@nowhere.com> wrote in message
news:OS**************@TK2MSFTNGP12.phx.gbl...
> Tell us perhaps more about what you need in this. I would pass only the > necessarty info as - as noted by Marina - it would be similar to

remoting

a
> connection.
>
> Perhaps could you use a web service ? What are you trying to achieve

? >
> Patrice
>
> --
>
> "Marina" <so*****@nospam.com> a écrit dans le message de
> news:e1**************@TK2MSFTNGP11.phx.gbl...
> > Remoting an HttpContext is kind of like trying to remote a SQL
> connection -
> > how could it possibly work? The HttpContext holds a live connection

to

> the
> > response stream as well as to the request stream - you can't
> > serialize/deserialize something like that.
> >
> > "Rob Morgan" <ro********@ode.state.oh.us> wrote in message
> > news:O9**************@TK2MSFTNGP11.phx.gbl...
> > > For some reason I can't pass the Context to my remoting object.

When

I

> run
> > > this the application just shows the thrown exception, it never

sends the
> > > Context it to the remoting server. If I only send the exception it > works.
> > > Any ideas appreciated
> > >
> > > protected void Application_Error(Object sender, EventArgs e)
> > > {
> > > ODE.Enterprise.Exception.Common.IExceptionHandler

exceptionHandler = > > > (ODE.Enterprise.Exception.Common.IExceptionHandler )
> > >
> >
>

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter > > > prise.Exception.Common.IExceptionHandler));
> > > exceptionHandler.RaiseError(Server.GetLastError(). InnerException, > > > System.Web.HttpContext.Current);
> > > }
> > >
> > >
> >
> >
>
>

[Rob Morgan]

Thank you very much for the help!

"Patrice" <no****@nowhere.com> wrote in message
news:#W**************@TK2MSFTNGP09.phx.gbl...

Just call your hanlder from the Application_Error event (available in
global.asax).

IMO there is no need to remote this. Just have the local handler create a
message and send it to the support team....

Patrice
--

"Rob Morgan" <ro********@ode.state.oh.us> a écrit dans le message de
news:OR**************@TK2MSFTNGP14.phx.gbl...

We will probably email it to our admins, or write it out to file, or
database it. I think your right, produce the trace message then send it.

What would be the best way to accomplish this?

"Patrice" <no****@nowhere.com> wrote in message
news:#b*************@TK2MSFTNGP09.phx.gbl...

Humm.. And what is the reason behind remoting the exception handler ? What do you do with the information once you handler retrieved it ? If this is

to

produce a trace message, you could perhaps produce the trace message and sends directly this information to the handler rather than to send this and

create the trace message at the other end.

Also what benefit are you trying to reach by remoting the handler ?

Patrice

--

"Rob Morgan" <ro********@ode.state.oh.us> a écrit dans le message de
news:O$*************@TK2MSFTNGP15.phx.gbl...
> I've made a remoting exception handler and I want applications to

send it

> enough information so we can route/track down the errors. I've got

it > accepting Server.GetLastError().InnerException, and I wanted to

include the
> context information. Looks like I'm going to have to send it the

Response,

> Request, and Enviroment objects if that's possible. The smaller amount of

> code that the applications have to use the better.
>
> Thanks
>
> "Patrice" <no****@nowhere.com> wrote in message
> news:OS**************@TK2MSFTNGP12.phx.gbl...
> > Tell us perhaps more about what you need in this. I would pass

only

the

> > necessarty info as - as noted by Marina - it would be similar to
remoting
> a
> > connection.
> >
> > Perhaps could you use a web service ? What are you trying to

achieve ? > >
> > Patrice
> >
> > --
> >
> > "Marina" <so*****@nospam.com> a écrit dans le message de
> > news:e1**************@TK2MSFTNGP11.phx.gbl...
> > > Remoting an HttpContext is kind of like trying to remote a SQL
> > connection -
> > > how could it possibly work? The HttpContext holds a live connection to
> > the
> > > response stream as well as to the request stream - you can't
> > > serialize/deserialize something like that.
> > >
> > > "Rob Morgan" <ro********@ode.state.oh.us> wrote in message
> > > news:O9**************@TK2MSFTNGP11.phx.gbl...
> > > > For some reason I can't pass the Context to my remoting

object. When

I
> > run
> > > > this the application just shows the thrown exception, it never

sends

> the
> > > > Context it to the remoting server. If I only send the

exception it

> > works.
> > > > Any ideas appreciated
> > > >
> > > > protected void Application_Error(Object sender, EventArgs e)
> > > > {
> > > > ODE.Enterprise.Exception.Common.IExceptionHandler

exceptionHandler

=

> > > > (ODE.Enterprise.Exception.Common.IExceptionHandler )
> > > >
> > >
> >
>

ODE.Enterprise.Exception.Common.ClassFactory.Creat eInstance(typeof(ODE.Enter > > > > prise.Exception.Common.IExceptionHandler));
> > > >

exceptionHandler.RaiseError(Server.GetLastError(). InnerException, > > > > System.Web.HttpContext.Current);
> > > > }
> > > >
> > > >
> > >
> > >
> >
> >
>
>