I've now installed it on a third platform (Win2k/IIS/.netFWv1.1SP1) and it
did put the module in the GAC, however, it didn't place the dll on the system
and the codebase location is blank on the module. If you do the manual steps,
you will have the dll on the system and the codebase location is set to the
dir of the dll.
So, I'm confused if the dll is actually intended to be on the system or not
to ensure the GAC module is working.
Also, I figured out the Installer issue and I can extract it OK now.
> I've done a couple machines, and other than causing a conflict with
> CAS in Reporting Services I have not had any problems. The module
[quoted text clipped - 3 lines]
> Scott
> http://www.OdeToCode.com/
Dan Kahler - 18 Oct 2004 17:12 GMT
The GAC isn't really intended to be viewed this way, but if it'll help you
sleep better, you can verify that the DLL actually is on your system by
going to command-line and navigating through the
"<systemroot>\Assembly\GAC\Microsoft.Web.ValidatePathModule" folder
structure.
Once you've done that, forget that this technique exists - nothing good can
come from circumventing the .NET Framework admin tools or Windows shell
hooks, so you definitely don't want to do this regularly.
Dan Kahler
> I've now installed it on a third platform (Win2k/IIS/.netFWv1.1SP1) and it
> did put the module in the GAC, however, it didn't place the dll on the system
[quoted text clipped - 13 lines]
> > Scott
> > http://www.OdeToCode.com/