Take MediaWiki, it is GPL licensed (not AGPL), so you can modify it and run an instance of it without sharing your changes. Except, when someone accesses it, you are redistributing MediaWiki's GPL-licensed JavaScript files to their browser, so you do have to share your changes[0]. Think how many sites there are violating that without even realising.
Now think how you configure MediaWiki; you modify LocalSettings.php to (at the bare minimum) add the database username/password, and set the secret key.
This means essentially every site running a MediaWiki installation (or Wordpress, or effectively any other GPL-licensed web application) is violating the GPL, and are only getting away with it because no one has bothered to take legal action over it.
[0] http://lwn.net/Articles/609709/ (section: "JavaScript and the GPL")
However, once you distribute the JavaScript files:
"You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License [...] These requirements apply to the modified work as a whole."
By modifying LocalSettings.php you have created a derivation. By redistributing the JavaScript files you have distributed part of the work and therefore must make the whole derived work available under the GPL.
If the thing you want to use is a DLL, how do you use it without linking to it? Writing some sort of external process and using IPC to talk to it might fulfill the letter of the license, but it's more work and less robust, and still violates the spirit of the GPL.
In the end, we picked the MIT licensed component and worked around the issues.
That's not so hard, is it?
It's just like the question you get when using proprietary software. If you don't want to pay the license fee or abide by its terms and conditions, you find an alternative or write an alternative yourself.
The obligation to release your code is just the license fee for the GPL. If that's too steep for you, look somewhere else.
No one can force you to open your whole code base. They can only make you choose between opening the parts that do the unsafe things listed above (linking, running in the same address space, utilizing private data structures via some kind of shim that is supposed to work around the GPL), or they can force you to stop distributing the GPLed software.
It's so stunningly easy to use GPLed software properly, and there are thousands of companies doing it. Just don't link it to your code, or try to do some kind of hack that avoids linking it while giving you all of the same benefits of doing so.The problem with VMware is that they have been pushing all of the boundaries; rather than just taking the easy road and doing known safe things like ensuring that there's a clear separation between GPLed code and their code, or just releasing their code that is linking to the GPLed code.