There a few ways to accomplish this. When using multiple computers to factor Mersenne Primes I simply sent the source code from the server to the client and dynamically compiled the code as needed.
Something to this affect. Dim JobCode as string= MyWebService.GetNextJobCode() Dim Result as string = Eval(JobCode) MyWebService.ReportResults(Result) You can find the Eval() function here http://www.codeproject.com/KB/dotnet/evaluator.aspx If you want to stick with assemblies. You can do with something like this Dim JobXml as string= MyWebService.GetNextJobCode() which returns an xml document like this <job> <methodname value="MyMethod"> <params> <param number="1" value="myInput1" /> <param number="2" value="myInput2" /> </params> <assemblyurl value="http://mydomain.com/myassembly.dll"; /> </job> ' Something like this untested.... The use a web client to download the assembly. Assem = Assembly.load(lLcationOfDownload) Dim T as Type = Assem.GetType() Dim M as MethodInfo= T.GetMethod(MethodName) Dim Result as Object= M.Invoke(new Object() {Param1.Value, Param2.Value}) And finally a third and possibly most easiest.. but most hackish.... Download the Dll into the bin folder of a web app and code for an ASPX Web Form that executes your code and request the page... For Example Dll Code is imports 'whatever Namespace MyNameSpace Public Class MyClass Public Shared Sub MySub for j as integer= 0 to 1000 response.write(j & "<br />") next End Sub end class On Oct 14, 11:51 am, Andrew Badera <[email protected]> wrote: > Why do you need the fullblown assembly? Can't you just share > interfaces? I guess I don't understand enough about the need here. > > Using interfaces that describe the objects, you can distribute a common > library. > > That's a major aspect of the concept of services -- web, remoting, > WCF. You have shared interfaces defining operations and objects. > > ∞ Andy Badera > ∞ +1 518-641-1280 > ∞ This email is: [ ] bloggable [x] ask first [ ] private > ∞ Google me:http://www.google.com/search?q=andrew%20badera > > On Wed, Oct 14, 2009 at 9:59 AM, Pat <[email protected]> wrote: > > > Andy, > > > Thanks for writing. I believe you, but I'm still stuck, then. > > > As described above, I need a way to have compiled DLLs on one machine > > able to run on another, and the client program on the machine running > > them will never know which ones they are. They will all be run from a > > single client that I have written, though. > > > What are the better ways to accomplish this, if not the way I > > described > > here:http://www.vbdotnetheaven.com/UploadFile/rahul4_saxena/Reflection0912... > > ? > > > TIA! > > > :) > > > On Oct 13, 3:39 am, Andrew Badera <[email protected]> wrote: > >> What you're talking about doing is potentially extremely dangerous! > >> Elevation city! Even if it's internal, you're not just opening a door > >> you don't want to open -- you're CREATING a door that shouldn't be > >> there.
