I have done the same thing as Mark had said, but I wanted to avoid that.
Neways, this seems the only way out.
level variable application("DLLNAME").
have achieved it. So while deploying other versions I will need to change
"Mark Schupp" <mschupp@ielearning.com> wrote in message
news:uVmJHSMlDHA.1676@TK2MSFTNGP09.phx.gbl...
> You cannot do this with VB components but you should be able to do it with
> C++ components. You'll have to set up different versions in the registry.
> For an example of how this works have a look at the MSXML2.XMLHTTP object
in
> the registry. You will probably see at least 2 versions.
>
> CreateObject("msxml2.xmlhttp") will give you the "standard" version.
> probably 3.0
> CreateObject("msxml2.xmlhttp.2.6") will give you the 2.6 version
> CreateObject("msxml2.xmlhttp.3.0") will give you the 3.0 version
> CreateObject("msxml2.xmlhttp.4.0") will give you the 4.0 version
>
> Put the desired ProgIDs in an include file so you can change them easily.
>
> If the objects are in VB components you will need to change the project
and
> DLL name and recompile the dlls. Then put the new ProgID in an include
file
> as above. For example:
>
> CreateObject("somedll1.someobject") version 1 application
> CreateObject("somedll2.someobject") version 2 application
>
> --
> Mark Schupp
> Head of Development
> Integrity eLearning
>
www.ielearning.com >
>
> "ack" <akshay49@hotmail.com> wrote in message
> news:OyPk0zGlDHA.2536@tk2msftngp13.phx.gbl...
> > Is there no way by which i can specify which version of the dll to
load?
> >
> > As far as i believe, when a dll registered it creates the entries in the
> > registry storing all the information like GUIDs, Threading Models etc,
> > including path.
> >
> > I am not sure if i understand the COM model exactly, but still these are
> my
> > thoughts
> >
> > Shld thr be any mechanism by which one wld be able to load the
appropriate
> > info.
> >
> >
> >
> > "Ray at <%=sLocation%>" <myfirstname at lane 34 . komm> wrote in message
> > news:uefm5gGlDHA.2528@TK2MSFTNGP10.phx.gbl...
> > > You could give them different class names. You can't register the
same
> > name
> > > twice, afaik, so they'd have to have different names. The other
option
> is
> > > to put the new dll on your test server. Test server? Come on, we all
> > have
> > > piles of test servers all over the place. ;]
> > >
> > > Ray at home
> > >
> > > "ack" <akshay49@hotmail.com> wrote in message
> > > news:uo%23PbfGlDHA.2616@TK2MSFTNGP11.phx.gbl...
> > > > Hii all,
> > > >
> > > > I have a this internal use portal i am working on deployed on a
> server.
> > > > My app uses some dlls that are instantiated from the asp pages using
> > > > server.createobject
> > > > Now I want to deploy the new versions of the web app on the same
> machine
> > > for
> > > > testing thus making production and staging machines same, running
the
> > > actual
> > > > site as well as test site
> > > > I have modified the dlls. So I want the old site to use old dll and
> new
> > > site
> > > > to use newer version
> > > >
> > > > IIS 5,, W2K
> > > >
> > > >
> > > > How can I?
> > > >
> > > > Thank U in advance
> > > >
> > > > ak
> > > >
> > > >
> > >
> > >
> >
> >
>
>