Re: ProgID in .NET?
- From: Boris <boris@xxxxxxxxxxx>
- Date: Fri, 14 Sep 2007 21:17:22 +0300
On Fri, 14 Sep 2007 18:47:33 +0300, ajk <ak@xxxxxxxxxxxx> wrote:
On Fri, 14 Sep 2007 11:58:30 +0300, Boris <boris@xxxxxxxxxxx> wrote:
As many of you know probably you can use ProgIDs in COM to instantiate COM
objects. The ProgID has the form Project.ClassName.Version. Thanks to
version it is possible to instantiate COM objects from different versions
of the same library. I wonder now if this is possible in .NET, too?
When a class from a .NET assembly is instantiated its namespace and class
name are used. Now if there is a new version of the .NET assembly you
obviously have name ambiguity as namespace and class name are the same. It
doesn't seem like it is possible to reference two versions of the same
assembly if namespace and class names are the same? Or is there any way of
specifying in code from which assembly the class should be instantiated?
Boris
so why don't u just add the version number in the namespace? then you
get the same effect?
The nice part about COM is that you can choose as a developer if you want to use a specific version of a COM object or not without the vendor of the DLL facing the problem we ran now into: If we don't change the namespace you can't use different versions in the same process. If we change the namespace customers who simply want to upgrade must modify their code.
Boris
.
- Follow-Ups:
- Re: ProgID in .NET?
- From: SvenC
- Re: ProgID in .NET?
- References:
- Re: ProgID in .NET?
- From: ajk
- Re: ProgID in .NET?
- Prev by Date: Re: dependecies for mfc exe
- Next by Date: Re: ProgID in .NET?
- Previous by thread: Re: ProgID in .NET?
- Next by thread: Re: ProgID in .NET?
- Index(es):
Relevant Pages
|