Has the assembly been strong named? not strong naming COM+ objects in .net
can give un-predictable results.
--
Simon Hart
Visual Developer - Device Application Development MVP
http://simonrhart.blogspot.com
"Ramon" wrote:
Quote:
Hi,
We've build a new standard PC for a developper that collaborates with us:
Windows XPSp2 Professional, VisualStudio 2005, IE 6.0, SQL Server Developper
editionetc...
When he tries to register a dot net com+ services component (in Com+) dll,
the registration hangs and the CPU gets crazy and gets at 100%.
If we force the program to close, we see that the dll finnally is registered
(even if we force the program to close when it is hanged).
What can be the cause of this problem?
Thanks in advance for your answer |