ok, MS was huge on toting that with .NET, DLL hell was a thing of the past. I beg to differ!
We're trying to get our logic layer in line, but we're finding that the new non-registry way of using DLL's does have a few drawbacks (and also just acts plain wonky). I think I'll put together a little faq eventually on the topic, but in the meantime lets all use this to post frustrations, solutions, and warnings about using the "new" dll scheme.
Here's the first thing to watch out for:
Back in the day, DLL's were registered with Windows. This caused probs if the dll was ever deleted or moved.
So now, to help prevent this, when you reference a dll, a local copy of that dll is made (meaning, if you have 10 projects referencing an ADO DLL you created, you'll have 10 copies of that DLL floating around). It also means that if you ever update that dll, you'll have to re-reference ALL 10 of those dll's in those 10 projects (is it starting to sound a bit silly?).
Now, I am by no means an expert, and I'm sure using things like the GAC there are ways around this. But since there's no stellar documentation out there yet, we're stuck with fumbling through it.
K, I think I feel better.
Anybody have tips/frustrations with the new dll scheme? Post em' here. Eventually we'll all crawl out of DLL-Hell together.
Jack
We're trying to get our logic layer in line, but we're finding that the new non-registry way of using DLL's does have a few drawbacks (and also just acts plain wonky). I think I'll put together a little faq eventually on the topic, but in the meantime lets all use this to post frustrations, solutions, and warnings about using the "new" dll scheme.
Here's the first thing to watch out for:
Back in the day, DLL's were registered with Windows. This caused probs if the dll was ever deleted or moved.
So now, to help prevent this, when you reference a dll, a local copy of that dll is made (meaning, if you have 10 projects referencing an ADO DLL you created, you'll have 10 copies of that DLL floating around). It also means that if you ever update that dll, you'll have to re-reference ALL 10 of those dll's in those 10 projects (is it starting to sound a bit silly?).
Now, I am by no means an expert, and I'm sure using things like the GAC there are ways around this. But since there's no stellar documentation out there yet, we're stuck with fumbling through it.
K, I think I feel better.
Anybody have tips/frustrations with the new dll scheme? Post em' here. Eventually we'll all crawl out of DLL-Hell together.
Jack