Today we noticed a situation while trying to register an assembly in COM+ 2 ways.

By accident one guy from our team used the following way, using network share:
>regsvcs \\<MachineIP>\<ShareName>\MyAssembly.dll
where "\\<MachineIP>\<ShareName>" is a share on the local machine. This command installed the assembly in COM+, however, did not use the Application/Package name specified in the Assemblyinfo file. But created a new application by name of the assembly itself on COM+

When we changed it to an absolute path
>regsvcs C:\MyAssembly.dll, it installed the assembly into the package name specified in Assemblyinfo file.

Any ideas on what contributed to this behaviour? Has it got anything to do with the user account that regsvcs uses to access the component assembly file (.dll) over the network?

Thanks
Jemima.