Component reuse

  • Thread starter Thread starter Rejeesh
  • Start date Start date
R

Rejeesh

Hi..

What all things need to be done to distribute custom components? i.e.
component created in one machine can be used with Embedded XP tools in
another machine?

Thanks,
Rejeesh
 
Hi,
What all things need to be done to distribute custom components?
Click to expand...

There are no special things that you can do.
Copy files that constrain your components and subfolders. Or zip them. User will have to import components manually from CDBM.

You can't make QFE like MS? I asked if we can use weupdate.exe but unfortunately it is forbidden.(They did not think about it so
far)

Please you should also ask for this feature:
http://msdn.microsoft.com/embedded/community/community/feedback/feedxp/default.aspx

Regards,
Slobodan
 
There are some thing you may do to automate the component distribution process to make it easy to install on a separate machine.

CMI object model allow you to make self installing packages. That means you will just have run the exe and it will install
everything to the database and repository automatically (pretty much the same as MS QFE packages do).
You don't really need the weupdate.exe in your package.

You can even think of a backup and rollback process for the setup.

One theoretically simple way (not to dig much into the CMI itself) would be to create a script to be used with CMIExplorer to
install new SLDs in to the Mantis DB.
 
Thanks for info.
Interesting I will have to look at this when I get some time, since I really needed this.

Regards,
Slobodan
 
Just a bit more info to save you some time....

Look at the ICMI interface (CMI class).
These are the methods you would really need for automating a new component import from within your "setup" applicaiton:
- OpenDB(ServerName, cmiDBReadImport)
- ImportCarrier(SLDPaths) (to import SLD files). Also CheckCarrier(SLDPaths) will help you to check the SLDs first.
- CloseDB()

For the events, DCMIEvents disp interface of CMI class, you may be interested to set your own handler for the
OnImportRepository(SrcRoot, DstRoot, SrcPath, RepositoryVSGUID, RepositoryDisplayName) and OnImportObject(SLDPath, TotalObjects,
ObjectsCompleted, ObjectType, ObjectDisplayName).
 
Thanks for the help..

There is not much documnentation available for CMI component. But I found an
article at http://www.windowsfordevices.com/articles/AT2652672892.html

Regards,
Rejeesh

KM said:
Just a bit more info to save you some time....

Look at the ICMI interface (CMI class).
These are the methods you would really need for automating a new component
Click to expand...
import from within your "setup" applicaiton:
- OpenDB(ServerName, cmiDBReadImport)
- ImportCarrier(SLDPaths) (to import SLD files). Also
Click to expand...
CheckCarrier(SLDPaths) will help you to check the SLDs first.
- CloseDB()

For the events, DCMIEvents disp interface of CMI class, you may be
Click to expand...
interested to set your own handler for the
OnImportRepository(SrcRoot, DstRoot, SrcPath, RepositoryVSGUID,
Click to expand...
RepositoryDisplayName) and OnImportObject(SLDPath, TotalObjects,
ObjectsCompleted, ObjectType, ObjectDisplayName).
Click to expand...
unfortunately it is forbidden.(They did not think about it
 
Rejeesh,

Pretty interesting article. I wish I would have seen it when I started digging into the CMI :-)
Anyway, thanks for the link.

Regarding CMI.. Yes, it is undocumented :-(
Some CMI scripts I posted in this NG so you may want to search.
Also, the XPeTools package (www.xpefiles.com) may help you to explore CMI as well.

Regards,
KM
 
Back
Top