The stackoverflow link indicates that it is an assembly versioning
problem, so the manifestation of the bug could conceivably depend on
details of the local environment in which it was built.  I forget /
don't know all the nitty gritty details of .net assembly binding and
versioning, but it seems that having a bad/wrong version of
sharpziplib in the GAC might be able to cause this kind of screwup.

On Jul 21, 1:25 pm, Dario Quintana <conta...@darioquintana.com.ar>
wrote:
> Weird, I think the script is the same for both NH and NHV

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to nhusers@googlegroups.com
To unsubscribe from this group, send email to 
nhusers+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to