Post by watercoolerwarrior on Aug 23, 2008 20:51:11 GMT
I've downloaded the EagleWare binaries and I'm using them to do some basic stuff from PowerShell - parsing shiparch/weapon_equip for report generation. PowerShell exists in an OS system folder, and although I can load the assemblies directly interactively, the IniParser chokes when I try to load an INI file since it can't find the GeneralNonsense DLL (I'm loading with Reflection.Assembly's LoadFile method).
I've been able to work around this by just running gacutil against the lot and then doing a quick-and-dirty LoadWithPartialName. IIRC, this is one of those weird problems that true applications don't encounter, since they'll actually import a copy of the DLL to the application's base directory. That's not possible with PowerShell (and is very un-script-like). Although this isn't exactly the kind of use you intended (nor a problem truly specific to the EagleWare binaries), do you recall a workaround that requires neither copying the EagleWare files to the PowerShell directory nor using gacutil?
The other option I considered was just merging all of the binaries. I don't like doing that, either, though, since it strikes me as an ugly hack. There are Good Reasons for keeping those binaries distinct; the entire coding process is cleaner.
I've been able to work around this by just running gacutil against the lot and then doing a quick-and-dirty LoadWithPartialName. IIRC, this is one of those weird problems that true applications don't encounter, since they'll actually import a copy of the DLL to the application's base directory. That's not possible with PowerShell (and is very un-script-like). Although this isn't exactly the kind of use you intended (nor a problem truly specific to the EagleWare binaries), do you recall a workaround that requires neither copying the EagleWare files to the PowerShell directory nor using gacutil?
The other option I considered was just merging all of the binaries. I don't like doing that, either, though, since it strikes me as an ugly hack. There are Good Reasons for keeping those binaries distinct; the entire coding process is cleaner.
