COM+ versioning

Hello-

I am developing a .Net Enterprise Services COM+ component on
WindowsXP using VS2005.


Can I install this DLL in the Component Services under 2 different
applications? Can settings (not the class name) define different
versions on the same COM+ component? Can I do it without using COM+
partitioning?


Thanks


.

Relevant Pages

  • com+ versioning
    ... I am developing a .Net Enterprise Services COM+ component on ... Can I install this DLL in the Component Services under 2 different ...
    (microsoft.public.dotnet.framework.component_services)
  • Re: Python DLL in Windows Folder
    ... with the old DLL. ... the requirement for backwards compatibility is not normative. ... I can install in according to 2.6 is the System folder. ... applications", not "to ensure backward compatibility with the old DLL". ...
    (comp.lang.python)
  • Re: PSAPI.DLL Corrupt?
    ... I have none of these applications, nor do I have any other instance of ... but it also results in the same registration error. ... do not help with the install issue I'm seeing. ... It seems that this task creates a "working" dll ...
    (microsoft.public.windows.server.general)
  • Assembly version compatibility issue
    ... I have a common assembly DLL that's installed into GAC (using msi created by ... It contains classes used by all the applications we have. ... and install the newer DLL properly when it's deployed. ...
    (microsoft.public.dotnet.framework)
  • Assembly version compatibility issue
    ... I have a common assembly DLL that's installed into GAC (using msi created by ... It contains classes used by all the applications we have. ... and install the newer DLL properly when it's deployed. ...
    (microsoft.public.dotnet.framework.aspnet)