Groklaw - Digging for Truth

	When you want to know more...

Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines

ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

You won't find me on Facebook

Donate

No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.

What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments

Sponsors

Hosting:

On servers donated to ibiblio by AMD.

Webmaster

It should be noted, that MS has fixed this | 178 comments | Create New Account

Comments belong to whoever posts them. Please notify us of inappropriate comments.

It should be noted, that MS has fixed this

Authored by: celtic_hackr on Friday, April 20 2012 @ 06:52 PM EDT

It is no longer necessary to only have one copy of a DLL in the same directory.
The newer versions of Windows have versioning capability. I make use of this
with every software release I make.

There is plenty to bash MS about without spreading FUD. What was once true but
is no longer is still FUD, unless you qualify it with "at the time".
;')

[ Reply to This | Parent | # ]

Actually, that has nothing to do with an API

Authored by: Anonymous on Friday, April 20 2012 @ 09:01 PM EDT

The way windows looks for DLLs is well documented and if you're putting
something you're not sure should be shared in in c:windows it's just bad
coding (indeed, this is what caused the whole DLL hell mess).

There's many other ways to reliably load DLLs.

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )