With the current released version of EIF, the best (and sadly - the only)
practice is to install via the MSI (i.e. the EnterpriseInstrumentation.exe
- self extracting exe that contains an EnterpriseInstrumentation.msi).
Note: if you see the EIF readme.htm - it gives instructions on passing
switches into the install to specify to only install sub parts (e.g. dont
install the samples or documentation on the target machine)
If you manually install EIF - then it is unsupported by Microsoft. (If you
dont care, I can show you what the steps would be to manually install it).
The target production environment was server machines and not end-user
machines. It was thought that rolling out EIF onto server machines via an
MSI was acceptable. (I guess I can go along with this depending on the size
of the production environment).
Sorry I couldnt be of more help.
Mike
--------------------
| What is best practice for deploying EIF, is this
| described somewhere? I don't want to have to do a full
[quoted text clipped - 3 lines]
| GAC? I tried to play around with this but was getting
| errors when then trying to installutil my app.

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
BW - 13 Jul 2004 18:11 GMT
Thanks, Mike. I had not looked in the readme (doh!),
just the .chm file. Silent msi installation should be
fine for us.
>-----Original Message-----
>With the current released version of EIF, the best (and sadly - the only)
[quoted text clipped - 25 lines]
>| GAC? I tried to play around with this but was getting
>| errors when then trying to installutil my app.