com+ installation from msi package

[NewsArchive]

Hi Phil and All

The suggestion of making a Merge Module is good but how do i
import the Com+ application to the Merge Module ?

On my Com+ application i have about 65 DLL's all written in VB6,
and all are our Dll's non of third party (e.g Microsoft).
so how do i make a Merge Module for that application?

As you can see i am very confused here ,first i haven't done
a Merge Module before and second never registered a
Com+ application with ISWI 2.03.
I didn't find articles about how to do that maybe anyone knows
of such article or can point me to some guides.

Maybe the way is to install the component regularly and then
run some script to make the Com+ application and registered them
in to it?

So to make the question simple,what would be the best way to
install a Com+ application (on a WinServer 2000) that has over
then 65 components (VB6 components),and how to do that?

Thanks very much
Yoav




"Phil Wilson" <phil.wilson@unisys.nospam.com> wrote in message
news:3b6f0ee1@news.installshield.com...
> It would be much more manageable if you could export a merge module
instead
> of a .msi file.
>
> Suggestion: Windows Installer can merge databases. Try the WiMerge.vbs
> script in the SDK sample scripts. You would then have one .msi file that
> might be easier to massage to do what you want it to do.
>
> It would be normal for an installation to install and leave behind
Microsoft
> Dlls. They typically don't get uninstalled, so perhaps this is a MS Dll
> you're referring to.
>
> <Yoav Shabtai> wrote in message news:3b6d195c@news.installshield.com...
> > Hi All
> >
> > I am working with ISWI 2.03 on a WIN 2000 SP1 OS.
> >
> > I have a few question about Com+ installation and distribution:
> >
> > 1)-I would like to export a Com+ application located in the
> > 'Components Services'. for now i'm using the 'Export' option
> > which makes an msi file that install the Com+ application on the
> > target machine, i can edit the msi file using ORCA.
> >
> > Is there a way to do the installation with ISWI ?
> >
> > 2)-I'm installing the msi file within a nested installation ,is there a
> way
> > to pass the destination folder of the parent installation
> > to the child msi package?
> >
> > 3)-For some reason the msi package that was created with the
> > 'Export' option leaves behind some DLL that are still registered.
> > So in order to install a new Com+ msi package i have to unregister
> > the remaining DLL's manually.
> > What could be the reason that the msi file does that?
> >
> >
> > Any help would be just super
> > Thanks
> > Yoav
> >
> >
> >
> >
> >
>
>

[NewsArchive]

I don't know much about COM+, but I was thinking that the tool that exports
the MSI package could export a merge module instead, then you'd plug that
into your install. If you can't do that, and you're stuck with an MSI file
to install, it looks like you need a setup that will install your stuff, and
a custom action to initiate an embedded MSI file. There are articles on the
IS support site that describe how to do this (which I can't point you at as
Code Red paranoia has resulted in internet access here being suspended). You
can pass the required destination to the child install as a parameter to
msiexec, passing something like INSTALLDIR = [INSTALLDIR].

<Yoav Shabtai> wrote in message news:3b70eb2f@news.installshield.com...
> Hi Phil and All
>
> The suggestion of making a Merge Module is good but how do i
> import the Com+ application to the Merge Module ?
>
> On my Com+ application i have about 65 DLL's all written in VB6,
> and all are our Dll's non of third party (e.g Microsoft).
> so how do i make a Merge Module for that application?
>
> As you can see i am very confused here ,first i haven't done
> a Merge Module before and second never registered a
> Com+ application with ISWI 2.03.
> I didn't find articles about how to do that maybe anyone knows
> of such article or can point me to some guides.
>
> Maybe the way is to install the component regularly and then
> run some script to make the Com+ application and registered them
> in to it?
>
> So to make the question simple,what would be the best way to
> install a Com+ application (on a WinServer 2000) that has over
> then 65 components (VB6 components),and how to do that?
>
> Thanks very much
> Yoav
>
>
>
>
> "Phil Wilson" <phil.wilson@unisys.nospam.com> wrote in message
> news:3b6f0ee1@news.installshield.com...
> > It would be much more manageable if you could export a merge module
> instead
> > of a .msi file.
> >
> > Suggestion: Windows Installer can merge databases. Try the WiMerge.vbs
> > script in the SDK sample scripts. You would then have one .msi file that
> > might be easier to massage to do what you want it to do.
> >
> > It would be normal for an installation to install and leave behind
> Microsoft
> > Dlls. They typically don't get uninstalled, so perhaps this is a MS Dll
> > you're referring to.
> >
> > <Yoav Shabtai> wrote in message news:3b6d195c@news.installshield.com...
> > > Hi All
> > >
> > > I am working with ISWI 2.03 on a WIN 2000 SP1 OS.
> > >
> > > I have a few question about Com+ installation and distribution:
> > >
> > > 1)-I would like to export a Com+ application located in the
> > > 'Components Services'. for now i'm using the 'Export' option
> > > which makes an msi file that install the Com+ application on the
> > > target machine, i can edit the msi file using ORCA.
> > >
> > > Is there a way to do the installation with ISWI ?
> > >
> > > 2)-I'm installing the msi file within a nested installation ,is there
a
> > way
> > > to pass the destination folder of the parent installation
> > > to the child msi package?
> > >
> > > 3)-For some reason the msi package that was created with the
> > > 'Export' option leaves behind some DLL that are still registered.
> > > So in order to install a new Com+ msi package i have to unregister
> > > the remaining DLL's manually.
> > > What could be the reason that the msi file does that?
> > >
> > >
> > > Any help would be just super
> > > Thanks
> > > Yoav
> > >
> > >
> > >
> > >
> > >
> >
> >
>
>

[NewsArchive]

Hi,

I created an msi package using the com application export wizard. I want to
include it in my setup, so I followed the procedure Q105534 - HOWTO:
Installing COM+ Components.
I use Developer 7.02 and a basic msi project.

When the CA is launched, I get an error from the com+ package:
"<filename.dll> is not a valid short file name". The file name is longer
than 8 characters. According to the logfile, it happens at the installfiles
action. When I look in <program files>\complus applications\{...}, I see
that the file has been copied. Why do I get this error?

When I run the com+ msi myself by double clicking it, no errors occur and
the registration is perfect. So obviously the com+ package is ok.

Does somebody know what is going wrong?


Thanks,
Mario

[NewsArchive]

I understand the msi files created by COM export wizard don't have the
proper Short filename | Long file name entries in the File table. If you
stick to 8.3 files I don't think you get that error. There's a discussion
about it in microsoft.public.platformsdk.msi.

"Mario" <mario.cauwe@quadrat.be> wrote in message
news:3c230dac@news.installshield.com...
> Hi,
>
> I created an msi package using the com application export wizard. I want
to
> include it in my setup, so I followed the procedure Q105534 - HOWTO:
> Installing COM+ Components.
> I use Developer 7.02 and a basic msi project.
>
> When the CA is launched, I get an error from the com+ package:
> "<filename.dll> is not a valid short file name". The file name is longer
> than 8 characters. According to the logfile, it happens at the
installfiles
> action. When I look in <program files>\complus applications\{...}, I see
> that the file has been copied. Why do I get this error?
>
> When I run the com+ msi myself by double clicking it, no errors occur and
> the registration is perfect. So obviously the com+ package is ok.
>
> Does somebody know what is going wrong?
>
>
> Thanks,
> Mario
>
>
>

[NewsArchive]

Ok, thanks, I hadn't yet noticed that topic on the microsoft newsgroup.

"Phil Wilson" <phil.wilson@nospam.unisys.com> wrote in message
news:3c237912@news.installshield.com...
> I understand the msi files created by COM export wizard don't have the
> proper Short filename | Long file name entries in the File table. If you
> stick to 8.3 files I don't think you get that error. There's a discussion
> about it in microsoft.public.platformsdk.msi.
>
> "Mario" <mario.cauwe@quadrat.be> wrote in message
> news:3c230dac@news.installshield.com...
> > Hi,
> >
> > I created an msi package using the com application export wizard. I
want
> to
> > include it in my setup, so I followed the procedure Q105534 - HOWTO:
> > Installing COM+ Components.
> > I use Developer 7.02 and a basic msi project.
> >
> > When the CA is launched, I get an error from the com+ package:
> > "<filename.dll> is not a valid short file name". The file name is longer
> > than 8 characters. According to the logfile, it happens at the
> installfiles
> > action. When I look in <program files>\complus applications\{...}, I
see
> > that the file has been copied. Why do I get this error?
> >
> > When I run the com+ msi myself by double clicking it, no errors occur
and
> > the registration is perfect. So obviously the com+ package is ok.
> >
> > Does somebody know what is going wrong?
> >
> >
> > Thanks,
> > Mario
> >
> >
> >
>
>