Fernando P. Nájera Cano wrote:
> Hi,
>
> SK> Even though there are some examples on how to implement a shell
> SK> extension with .NET, you must not do that! A shell extension is
> SK> loaded by all applications that use the "Open File" dialogs. That
> SK> means if you have a shell extension written for e.g. NET2.0, and a
> SK> NET1.1 app opens the "Open File" dialog, NET2.0 code is injected
> SK> into that NET1.1 application. This can lead to some very ugly
> SK> crashes.
>
> SK> Even MS realized that problem and now suggests to write shell
> SK> extensions *not* with .NET anymore.
>
> Say bye-bye to DLL Hell, say hello! to .NET Hell :(
>
> Best regards,
>
> Fernando Nájera
Actually, if that is the case, if you have a .NET 1.1 application and
developed some sort of plugin architecture, and someone made a .NET
2.0-based plugin, wouldn't that cause the same problem? If so, that
really puts a damper on what type of applications can be written in .NET
(not just shell extensions - although an application crash isn't as bad
as an explorer.exe crash).
Also, you can make DLLs with .NET. A DLL is just a special type of
executable typically containing exported function names. Shell
extensions and other COM objects are usually DLLs. So, DLL Hell and
.NET Hell are now possible from within the same file. Nifty.
--
Thomas Hruska
CubicleSoft President
XLAuditor - Perform deep spreadsheet analysis quickly and easily. Find
the problems everyone else missed. Be the hero of your company today:
http://www.xlauditor.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Dec 13 21:11:54 2005