You know you've been working too long when it takes a minute or so to realize
that the intent of "PIA" was "pain in the ass" rather than "Primary Interop
Assembly"...
Wayne M. Bradney
Chief Application Architect, Derivatives & Structured Products
Wall Street Systems, 1290 Avenue of the A
Sounds like a good compromise. Strong naming can be a real PIA if you don't
actually want the "benefits" it brings.
Regards,
Neil Haughton BSc MIET IEng(CEI)
Development Manager
Autoscribe Limited
Wellington House
Riseley Business Park
Basingstoke Road, Riseley
Berkshire RG7 1NW
Office: +44
> A strong name includes the version number as well as the key.
And that's the problem. Any change that results in a new version # (even a
trivial build # jump) means you need to fix the references. I actually find the
GAC not very useful. Sure, core .NET files should be there, but I can drop th
A strong name includes the version number as well as the key.
Strong naming is also required for installation in to the GAC, which I find
useful for utilities such as
loggers.
2 cents,
Dan
Wouldn't they use the same private key across upgrades? I would assume
they would. The strong naming afaik is to ensure that people can't
create "unoffial" releases with the claim that they're official
releases. I figured it was for legal and integrity reasons.
Simon
> Because if you don't, surely you risk breaking existing applications
when you upgrade log4net?
You might. But that's a decision and assessment that I can make when I
choose to do the upgrade. I can (somewhat) see the point on two DLLs (or
DLL and EXE) that are part of the same package. Say t
Because if you don't, surely you risk breaking existing applications
when you upgrade log4net?
Regards,
Neil Haughton BSc MIET IEng(CEI)
Development Manager
Autoscribe Limited
Wellington House
Riseley Business Park
Basingstoke Road, Riseley
Berkshire RG7 1NW
Office: +44 (0) 118 984
I forget, is the "official" release strongly named? And if so, did those
other components reference it by strong name? I tend to hate strong
naming! It's a logging component, if there's an upgrade I should be able
to use it, why should I be tied to an older version just because you
built against th
