DLL problems / .NET solutions (?)

[douglass_davis]

Hello,

I keep reading about "DLL hell" and how it used to make sure that the
correct DLL is used, especially when installing a new program and
attempting to install the DLL that comes packaged with that program.

Then I read about how .NET makes DLLs easier and less error prone. I
really don't know any specifics on this though. What's so good about
..NET when it comes to DLLs?

Also, I haven't been able to find a good explanation of how the GUID
and version number works. In 1.2.3.4 for example, what does each
number represent? Any one know of a good web page explaining those?

thanks.

--
http://www.douglassdavis.com

[Brian Gideon]

Douglass,

I good place to start is the wikipedia article.

http://en.wikipedia.org/wiki/DLL_hell

It'll give you a definition and some background. There are good links
at the bottom of the article that explain how .NET fixes the problem.

Brian

do************@earthlink.net wrote:

Hello,

I keep reading about "DLL hell" and how it used to make sure that the
correct DLL is used, especially when installing a new program and
attempting to install the DLL that comes packaged with that program.

Then I read about how .NET makes DLLs easier and less error prone. I
really don't know any specifics on this though. What's so good about
.NET when it comes to DLLs?

Also, I haven't been able to find a good explanation of how the GUID
and version number works. In 1.2.3.4 for example, what does each
number represent? Any one know of a good web page explaining those?

thanks.

--
http://www.douglassdavis.com