Hmm ... Remote code should be loaded with remote permissions ;-) Storing it to file and loading it via Assembly.Load() brings a whole load of possible security problems. In fact, I could inject any code and it would run with full privileges.
-Ingo Author of "Advanced .NET Remoting" http://www.dotnetremoting.cc > -----Original Message----- > From: Deepak Rao [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 25, 2002 12:34 AM > To: [EMAIL PROTECTED] > Subject: Re: [DOTNET] Serializing an assembly > > > Why not just transfer the file over, save it to disk and do and > assembly.Load()? You could use remoting for transferring the file. And > no web server / web-server channel is required for this. > > Deepak > > > -----Original Message----- > > From: dotnet discussion [mailto:[EMAIL PROTECTED]] > On Behalf > Of > > Ingo Rammer > > Sent: Wednesday, April 24, 2002 5:40 PM > > To: [EMAIL PROTECTED] > > Subject: Re: [DOTNET] Serializing an assembly > > > > Hi Lorin, > > > > even if this is a somewhat weird approach, you could do the > following: > > > > First, look in the framework SDK: there's a > WebServer-Channel sink for > > Remoting at [1]. You can embed this to "simulate" a web > server with a > .NET > > Remoting server. > > > > Then you can use > > > Assembly.LoadFrom("http://your.Remoting.Server/SomeDirectory/Y > ourAssembl > y. > > dl > > l") at the client side to dynamically download the > assembly. [it will > > however run in a untrusted security context]. > > > > WARNING: This web server channel sink is an unsupported sample and > might > > pose one or another security problem. But it should get you started > ;-) > > > > (And of course, you could also publish the DLL with any http server, > like > > IIS and such. But you asked if it's possible with Remoting ;-)) > > > > just some ideas again, > > -Ingo > > > > [1] X:\Program Files\Microsoft Visual > > > Studio.NET\FrameworkSDK\Samples\Technologies\Remoting\Advanced > \ChannelSi > nk > > s\ > > WebServer > > > > Author of "Advanced .NET Remoting" > > http://www.dotnetremoting.cc > > > > > -----Original Message----- > > > From: Lorin Hochstein [mailto:[EMAIL PROTECTED]] > > > Sent: Wednesday, April 24, 2002 11:06 PM > > > To: [EMAIL PROTECTED] > > > Subject: [DOTNET] Serializing an assembly > > > > > > > > > Is it possible to serialize an assembly and transfer it to > > > another process > > > on another machine (say, via remoting calls)? I've looked and > > > looked, but > > > haven't found any references to such a thing. > > > > > > I'm working on a mobile agent project for a course, using > > > .NET. So far, > > > we've been moving the assemblies from one machine to another > > > by copying the > > > DLL, and then serializing the agent object and transferring > > > it to the other > > > machine via remoting calls. > > > > > > It seems cleaner if there was some way to transmit the > > > assembly without > > > doing a file transfer (serializing the agent object is still > necessary > > > because we need to maintain state). Is it even possible > to transmit > an > > > assembly from one process to another without copying a DLL? > > > > > > Lorin > > > > > > _________________________________________________________________ > > > Get your FREE download of MSN Explorer at > > > http://explorer.msn.com/intl.asp. > > > > > > You can read messages from the DOTNET archive, unsubscribe > > > from DOTNET, or > > > subscribe to other DevelopMentor lists at > http://discuss.develop.com. > > > > > > > You can read messages from the DOTNET archive, unsubscribe from > DOTNET, or > > subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com. You can read messages from the DOTNET archive, unsubscribe from DOTNET, or subscribe to other DevelopMentor lists at http://discuss.develop.com.
