ExternalStruct>>asObject being stripped

Have a packaging problem (4.01) where ExternalStructure>>asObject is getting
stripped (Method is part of "Active X Automation").  Tried adding the method
to the "must not strip" category to no avail.

Any ideas as to what can be done here?

Many thanks,

Chris Hayes

"Chris Hayes" <hayes@*zapthis*.creative-computing-inc.com> wrote in message
news:5yHS8.550$[hidden email]...
> Have a packaging problem (4.01) where ExternalStructure>>asObject is
getting
> stripped (Method is part of "Active X Automation").  Tried adding the
method
> to the "must not strip" category to no avail.
>
> Any ideas as to what can be done here?
>

OK.  Worked around this by moving the method out of "Active X Auto" and into
one of my application packages.   Not very elegant but got the job done.

Chris

Chris,

> Have a packaging problem (4.01) where ExternalStructure>>asObject is
getting
> stripped (Method is part of "Active X Automation").  Tried adding the
method
> to the "must not strip" category to no avail.
>
> Any ideas as to what can be done here?

I'm not sure it applies in this case [1] but you could try making the
"Active X Automation" package a specific pre-requisite of your deployed
application package, as well as adding the method to the "must not strip"
category.

IIRC the stripper removes what it thinks are unwanted packages before
stripping methods.  A loose method will disappear with it's package and the
category doesn't help if the method has already gone.

Ian

[1] I would have thought there would be lots of referenced classes in the
Active X Automation package that would have prevented the stripper marking
it as unwanted.

"Ian Bartholomew" <[hidden email]> wrote in message
news:affhlv$e2v14$[hidden email]...
> Chris,
>

> I'm not sure it applies in this case [1] but you could try making the
> "Active X Automation" package a specific pre-requisite of your deployed
> application package, as well as adding the method to the "must not strip"
> category.
>

That sounds like a good idea.  I didn't know that explicit prereqs were
possible but now I see that it's exposed under package properties->'manual
prereqs'->Edit.

Thanks, Ian.

Chris

Chris,

> > I'm not sure it applies in this case [1] but you could try making the
> > "Active X Automation" package a specific pre-requisite of your deployed
> > application package, as well as adding the method to the "must not
strip"
> > category.
> >
>
> That sounds like a good idea.  I didn't know that explicit prereqs were
> possible but now I see that it's exposed under package properties->'manual
> prereqs'->Edit.

FWIW I had to do the same thing for a COM DLL that exposed a vtable (derived
from IUnknown vs. IDispatch) interface.  In that case, it was the type
library analyzer that was getting zapped before its time.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]