Hello OliviuG,
Does error arise only during install? Does it Server component? Strong named?
VS 2005?
O> Just to clairy the issue is reproducing on some test environments,
O> while it works on others.
O>
O>
>> We use serviced components and we've changed the transaction settings
>> on the
[quoted text clipped - 7 lines]
>>
>> Is there an extra assemblyn depency which we've introduced.
---
WBR,
Michael Nemtsev :: blog: http://spaces.msn.com/laflour
"At times one remains faithful to a cause only because its opponents do not
cease to be insipid." (c) Friedrich Nietzsch
OliviuG - 04 Jul 2006 18:36 GMT
Thanks for the reply. Found the issue to be caused by the presence of the
.net 2.0 on the machine.
The installer was registering the assembly in the com+ catalog using the
System.EnterpriseServices.RegistrationHelper COM objects(from vbscript), so
it picking up the 2.0 version.
Thanks.
> Hello OliviuG,
>
[quoted text clipped - 23 lines]
> "At times one remains faithful to a cause only because its opponents do not
> cease to be insipid." (c) Friedrich Nietzsche