Re: Component reuse

From: KM (konstmor_at_nospam_yahoo.com)
Date: 11/03/04

  • Next message: Marc C: "Re: Damaged CD, help."
    Date: Wed, 3 Nov 2004 14:13:36 -0800
    
    

    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).

    -- 
     Regards,
            KM, BSquare Corp.
    > Thanks for info.
    > Interesting I will have to look at this when I get some time, since I really needed this.
    >
    > Regards,
    > Slobodan
    >
    >
    > "KM" <konstmor@nospam_yahoo.com> wrote in message news:ehxvtEewEHA.2676@TK2MSFTNGP12.phx.gbl...
    > > 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.
    > >
    > > -- 
    > >  Regards,
    > >         KM, BSquare Corp.
    > >
    > > PS. I wish MS makes CMI public.
    > >
    > > > Hi,
    > > >
    > > > > What all things need to be done to distribute custom components?
    > > >
    > > > 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
    > >
    > >
    >
    >
    

  • Next message: Marc C: "Re: Damaged CD, help."

    Relevant Pages

    • Re: Component reuse
      ... 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. ...
      (microsoft.public.windowsxp.embedded)
    • Re: Compiled model interface (cmi) installation
      ... >I use the design framework IC5.033 and want to install the cmi. ... I have to execute the script cmiExtract which should be located ... Do I have to install further software packages? ... normal product). ...
      (comp.cad.cadence)
    • RMI problem
      ... The example contains a program that instantiates the remote object on ... Where cmi is the actual object it is going to instantiate. ... Any ideas about what I forgot to install, ...
      (comp.lang.java.developer)
    • Re: Component reuse
      ... Regards, ... digging into the CMI :-) ... >> process to make it easy to install on a separate machine. ...
      (microsoft.public.windowsxp.embedded)
    • Re: Component reuse
      ... Regarding CMI.. ... Regards, ... >> ObjectsCompleted, ObjectType, ObjectDisplayName). ... > process to make it easy to install on a separate machine. ...
      (microsoft.public.windowsxp.embedded)