event you could write code that runs a .cmd/.bat file
> that copies the feature and its associated files to the TEMPLATE\FEATURES
> directory to install (and activate) the feature.
>
>
>
> Clayton James
>
> Data Cogs Information Technology
>
>
>
> _____
>
>
ursday, 20 December 2007 6:22 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] You can't have a hidden feature with an activation
dependency?
Hi Clayton,
You on fire with the OzMoss stuff. Good work! That's a really good
thing to do to get visibility for MVP etc.
Do you
2007 12:34 AM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] You can't have a hidden feature with an activation
dependency?
Hi Bill
You can create a feature receiver class that contains code when a
feature gets:
* Installed
* Activated
* DeActivated
* UnInst
he feature.
Clayton James
Data Cogs Information Technology
_
From: [EMAIL PROTECTED] on behalf of Ishai Sagi
Sent: Fri 14/12/2007 4:48 PM
To: listserver@ozMOSS.com
Subject: RE: [OzMOSS] You can't have a hidden feature with an activation
dependency?
Maybe use featu
Maybe use featureactived event?
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of Bill Williamson [EMAIL
PROTECTED]
Sent: Friday, 14 December 2007 4:34 PM
To: listserver@ozmoss.com
Subject: [OzMOSS] You can't have a hidden feature with an activation d
