remoting

问题 Given that both the client and the server need to know everything about the object being remoted, firstly is this tight coupling, and secondly can .Net Remoting work in any other way? 回答1: Not really answering your question, but if you want to loosen the coupling, you might look at WCF's NETTCP binding as an alternative. The client can create a proxy for the entities - this way you won't need to share any assemblies (notably Entities) between client and server. 来源： https://stackoverflow.com

问题 I'm am currently revising a plugin architecture so that it utilizes AppDomains. The main difference between my plugins and the many examples I have found online is that instead of the plugin running and sending its results back to the main application, my main application is the one sending information to the plugin. As it currently stands, I create an instance of the loader in a separate AppDomain. It then does all your normal initialization such as loading the plugin assembly. As this point

问题 I am currently trying to build a threaded cleanup script with powershell, initiated from an IIS. I have made a threaded "Kill process by owner" using powershell remoting, running from the same list of servers as my cleanup script, and that works no problem. $jobs = @() foreach ($comp in $comps) { $jobs += start-job -FilePath ("CleanupJob.ps1") -ArgumentList $comp, $username Write-Host "Started Job on: $comp" } foreach($job in $jobs) { $job | wait-job | out-null receive-job $job.ID } Remove

问题 Ok I've found a solution to this particular error message on here already. But my case is slightly different. There are no "non-public" or "static" methods in my code. All are public. What I'm trying to do is pass a FrameworkElement (more specifically a web browser control) that was created in one process over to another process for display and use. Also I'm not using (and would to avoid using) any of the framework 3.5 addin stuff. Fails at the following line everytime. fe =

问题 This is my Hello World Remoting App. using System; using System.Collections.Generic; using System.Text; namespace Remoting__HelloWorld.UI.Client { public interface MyInterface { int FunctionOne(string str); } } using System; using System.Runtime.Remoting; using System.Runtime.Remoting.Channels; using System.Runtime.Remoting.Channels.Tcp; namespace Remoting__HelloWorld.UI.Client { class MyClient { public static void Main() { TcpChannel tcpChannel = new TcpChannel(); ChannelServices

问题 I establish a persistent session then attempt to execute a script remotely using the following line: Invoke-Command -Session $Session -FilePath "FullStopBizTalkApp.ps1" -argumentlist $BizTalkMgmtDBConString, $ApplicationNameInBizTalk If I then execute: $_.Exception.ToString() I can see the following error: System.Management.Automation.ItemNotFoundException: Cannot find path 'C:\Users\tfs_service\FullStopBizTalkApp.ps1' because it does not exist. I am able to invoke commands from the same

问题 CruiseControl.net ships with the ability to connect to a CruiseControl.net server using .net remoting. I've been able to connect and achieve all we need - a much more advanced version of the CCtray. However, a project can be configured to ask for a buildReason, this is fulfilled by subscribing to the ICruiseServer.ForceBuildReceived event, which as an argument takes an object which allows the reason the be returned. http://www.opensourcejavaphp.net/csharp/cruisecontroldotnet/ICruiseServer.cs

问题 Hi I am trying to set up remoting in an AIR app. Does anyone know if I need to define a context-root in the compiler settings. Can't seem to find any articles about setting it up, only in flex. Thanks 回答1: compiler setting looks like: -services "X:\tomcat\webapps\blazeds\WEB-INF\flex\services-config.xml" however, if you want AIR to work over http you have to setup it abit different than a webapp. dunno why, but when using a webapp its enough to setup the flex-server on blazeDS or whatver

问题 I have the following code to connect to a remote machine and execute commands.It is working if I create a new session for each Invoke-Command call to the remote machine. I don't want to create a new session each time I use Invoke-Command as that will not scale for thousands of commands on hundreds of machines concurrently and session creation itself is a big overhead. I need a way so that I can reuse the same session object in the $session powershell variable for multiple Invoke-Command calls

问题 I've written a .Net component that runs in a COM+ application. The component inherits from ServicedComponent and is marked to run as a server process (because I need to maintain static data through activations from multiple consumers). Registration is done using RegAsm.exe: c:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe /codebase MyObject.dll The COM+ application was created manually and the component added after creation. If I instantiate my component from PHP the code works as