C++/CLI COM component deployment
- From: Volker Hetzer <firstname.lastname@xxxxxxxx>
- Date: Thu, 25 Jan 2007 16:19:10 +0100
Hi!
I've done my first little COM component (using the clr) and after signing, regasm and gacutil I can call it from vbscript.
set X = createobject("ComComponent.Class1")
msgBox X.Testfunktion(2)
But the problem we're facing is that for a real development of several components (currently existing as scripting components) we need to be able
to call them by their path names. The situation is this:
We want to use those components to extend a PCB CAD tool.
At any time several users work with several projects, each CAD-Tool session
works with one project only. We typically release our components first for one project/user combination only and after this "beta" test for all projects.
So, we have the following directory structure:
....\BETA.ComponentName.PCBName.Username
....\FINAL.ComponentName.ALL.ALL
Those directories sit in a shared network drive and we really can't afford
to register and "install" each component on each client PC. We will release
very often, on average daily.
I'm looking for a way that lets me instantiate a component in VBScript
like this:
Dirname = figurOutDirName(ComponentName, PCBName,Username)
set X = createobject(Dirname&"\whatever.something")
X.myMethod(...)
Is this possible?
Lots of Greetings!
Volker
--
For email replies, please substitute the obvious.
.
- Follow-Ups:
- Re: C++/CLI COM component deployment
- From: Ben Voigt
- Re: C++/CLI COM component deployment
- From: Brian Muth
- Re: C++/CLI COM component deployment
- Prev by Date: Re: best way to check the installation of mfc80 side by side
- Next by Date: Re: Building VC++ 8.0 code on a machine without Visual Studio 2005
- Previous by thread: How to Change Lparam before calling CallNextHookEx()?
- Next by thread: Re: C++/CLI COM component deployment
- Index(es):
Relevant Pages
|