robgruen's WebLog

Server activated objects (SAOs both singleton and singlecall) use threadpool magic to execute remoting calls on thread pool threads. See ThreadPool.QueueUserWorkItem in the docs. Also note that you can change the # of thread pool threads…the default is Read More...

We generally use "caspol.exe -s off" as a quick test to determine if .NET framework security plays a part in problems with managed components. It used to be that sometimes people would forget to run "caspol.exe -s on" to turn framework security on. Imagine Read More...

Thanks to rick for the title! We are seeing more and more people encountering: Q322975 BUG: Passing large quantities of data in .NET Remoting calls causes an unexpected exception to occur - http://support.microsoft.com/?id=322975 . As you can tell from Read More...

I was helping someone out with an issue the other day. Basically we were attempting to create an instance of an object within an AppDomain and then use that object. Unfortunately when casting the object from the object returned from CreateInstance to Read More...

Maybe you didn’t know, but you can generate a WSDL document for your remote object fairly easily. You can generate the contract XML directly or you can use soapsuds.exe to generate a proxy dll that you can share with your consumers. All you have to do Read More...