Re: VERY Frustrated
From: Stark Frost (projects_at_dmgstudios.co.za)
Date: 06/03/04
- Next message: Stark Frost: "Re: VERY Frustrated"
- Previous message: Stark Frost: "Re: Does Marhsall-by-Reference still use a proxy?"
- In reply to: Elp: "Re: VERY Frustrated"
- Next in thread: Stark Frost: "Re: VERY Frustrated"
- Reply: Stark Frost: "Re: VERY Frustrated"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 3 Jun 2004 11:36:09 +0200
Hey Elp
Thanks for your reply.
I built the solution and then executed the server.exe file and set my client
project in vs.net as my startup project and did the debug. The program hangs
for about 7 seconds and then tells me that "The underlying connection was
closed: The remote name could not be resolved" and then it gives me an error
at the line of code:
-- MessageBox.Show(Me.theManager.getHash())
and a vs.net message box that says:
"An unhandled exception of type 'System.Net.WebException' occured in
mscorlib.dll
Additional information: The underlying connection was closed: The remote
name could not be resolved."
So i'm assuming that it raises an exception because the connection was
closed and therefore the line of code cannot complete its task.?
So my initial thought is that i have to change some settings to suite my
local environment, but the tutorial (see link in initial post) doesnt say
anything about changing any parameteres. Perhaps you could copy and paste
this project to see if it works on your system?
I'm very eager to get into Remoting but i just cant get hold of enough
resources anywhere so i have to do this the hard way. Your help will be
greatly appreciated.
Stark
"Elp" <rockfamily@REMOVEME.hotmail.com> wrote in message
news:OJM34KMSEHA.3840@TK2MSFTNGP09.phx.gbl...
>
> "Stark Frost" <projects@dmgstudios.co.za> wrote in message
> news:c9kij9$3fr$1@ctb-nnrp2.saix.net...
> > Hi there,
> >
> > Could someone please check out this tutorial and tell me why windows
asks
> me
> > if i want to debug the client program everytime i try to run it (built
> > version(exe)).
>
> This means that there has been an unhandeld exception in your application
> and that it crashed. This has nothing to do with .NET Remoting (although
the
> exception may have been caused by your .NET remoting component as well as
by
> anything else in your application). To solve the problem, compile your
> application in Debug mode and run it from Visula Studio (press the F5
key).
> When the unhandled exception will be raised, VS will tell you what it is,
> the stack trace and if available the line of code that caused the
exception.
> From there, you'll be able to find out what's wrong in your code.
>
> Note that with .NET Remoting, both the server and the client application
can
> run on the same computer (and also on different computer). This means that
> you can launch both the server and client app in Debug mode from VS on the
> same computer.
>
>
- Next message: Stark Frost: "Re: VERY Frustrated"
- Previous message: Stark Frost: "Re: Does Marhsall-by-Reference still use a proxy?"
- In reply to: Elp: "Re: VERY Frustrated"
- Next in thread: Stark Frost: "Re: VERY Frustrated"
- Reply: Stark Frost: "Re: VERY Frustrated"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|