Has anyone experienced the manifest utility removing the first character from your post processor DLL? I created a custom post processor class, DeleteOldLogsAndVersionsPostProcessor, in an assembly and DLL named PRAUpdater.dll. But the name attribute in the manifest chops of the first character of the DLL name to RAUpdater.dll. Here's the snippet from the manifest file:
<postProcessor type="PRAUpdater.PostProcessors.DeleteOldLogsAndVersionsPostProcessor" assembly="PRAUpdater, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" name="RAUpdater.dll" /></ServerApplicationInfo>
Any help greatly appreciated.
Thanks,
Sam

Signature
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
Sam Santiago - 31 Jul 2004 06:17 GMT
I was able to figure it out. All files, including your Post Processing assembly, must reside in or in a directory underneath the Update Files Folder specified when you generate the manifest file. This is due to the function ExtractRelativePath in the ManifestSettings class that expects this configuration.

Signature
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com
http://www.SoftiTechture.com
_______________________________
Has anyone experienced the manifest utility removing the first character from your post processor DLL? I created a custom post processor class, DeleteOldLogsAndVersionsPostProcessor, in an assembly and DLL named PRAUpdater.dll. But the name attribute in the manifest chops of the first character of the DLL name to RAUpdater.dll. Here's the snippet from the manifest file:
<postProcessor type="PRAUpdater.PostProcessors.DeleteOldLogsAndVersionsPostProcessor" assembly="PRAUpdater, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" name="RAUpdater.dll" /></ServerApplicationInfo>
Any help greatly appreciated.
Thanks,
Sam
--
_______________________________
Sam Santiago
ssantiago@n0spam-SoftiTechture.com