I am automating our deploymnet using CC.n开发者_StackOverflow中文版et and a NANT build script. I have to stop and start our COM+ components during deployment.
The title basically summarizes it. I have a COM+ Server Application implemented using VB.NET 2010, that was configured to gather data from its own .config file by using the procedure described in ht
Our Test web server recently went down and we lost COM+ Applications installations.I am trying to reinstall the COM Applications.I have the installed the COM Applications and have the Identity set to
I have this function (COM+) object that does all the encryption, but when it get\'s too many requests at once, it error\'s out and crashes. I get errors like \'Page On End Error\' and stuff like that
I want to know what are the different technologies available for communication among software components distributed across networked computers?
I have written a COM+ component in .NET 3.5 on a Windows 7 machine.Unfortunately, after I had programmed everything I came to know that the server where this component should reside is a windows 2003
I\'ve been trying to get a program that worked on Windows 2000 to work on Windows 2003.Everything I\'ve had to do so far to get the p开发者_运维知识库rogram to work on Windows 2003 has had to do with
I have a COM+ application that I wrote using C#.I have the assembly strongly named & signed.I want the application to use a library project & a 3rd party dll (log4net) but I don\'t want to pla
We have some COM+ code written in everybody\'s favourite language(?) -- VB6. This COM+ component calls into a standard COM component written by a 3rd party which performs calls into a SQL Server datab
I\'ve created a .NET 2 COM+ component to be consumed by our archaic classic ASP website. This is done quite simply in classic ASP...
加载中,请稍侯......