This is the first time I\'ve create a .NET Serviced Component (COM+) and I\'m having some issues when it comes to scalability. I\'ve stress tested it up to 4000 users but it is still failing to exceed
I\'ve created a COM+ server application and the call开发者_如何学Cer can\'t access it - when it tries to instantiate a COM object (CoCreateInstance()) from that application the following appears in sy
I am converting PPT to images using ASP.NET code. When i run my code Directly (no IIS 7.0 involved) its runs perfect. But when i configure my application to IIS 7.0 and then run the application its gi
In a small test project I have this code: HRESULT hr = CoCreateInstance(CLSID_DOMDocument, NULL, CLSCTX_ALL, __uuidof( IXMLDOMDocument ), ( void ** ) & m_pDoc);
I was updating a COM+ application, when an error showed up, saying that it couldn\'t be changed.Now, whenever I go into properties on one of the components in that application, or the properties for t
I have the following code in my C# class which remotely connects to a COM+ server on a remote machine.
I have a managed COM out of process server exe in c# exposing my application object model for automation everything is working fine. I can access it from unmanaged code (for example, VC++) and it star
I have a problem using Entity Framework and COM+. The architecture is this: A windows service calls four methods of a COM, every n minutes.
14 years ago when I was a green horn, setting up the components for classic ASP was not in my pay grade...Now however, I have gone back to the futur开发者_JAVA百科e and I find myself having to maintai
In my program I create Com+ objects dynamicly (late binding) using Type comObjectType = Type.GetTypeFromProgID(progId, true);
加载中,请稍侯......