Devil.NET announcement
I promise!
There will be a new release of Devil.NET in the next month and I hope to be able to fix all the bugs (specially the vflip one!).
The greatest app ever, evolved!
Laugh, if you want.
But really this is one of the major reasons we are using Windows today. Back in the days Windows (2.x) was not really popular and some applications (most notably Excel) had to redistribute a small Windows with themselves.
Then came Windows 3.0. And 3.1. And everybody dropped WordPerfect and 1-2-3 for Word and Excel so that they could Alt+Tab/Ctrl+Esc* to Solitaire instead of working. And Solitaire is still today the symbol of losing time instead of doing your job.
Greatest app of all times.
(*) If I’m not wrong, Alt+Tab was introduced with Windows 3.1, so the poor Windows 3.0 user had to switch with Ctrl+Esc.
P.S. Thanks DOSBOX for making this possible. And also for running my favorite games.
Shell extensions in C# and/or VB.NET
Please, repeat with me.
I WILL NEVER WRITE SHELL EXTENSIONS IN C# OR VB.NET.
Not even if Dino Esposito suggests it.
It’s bad for many reasons.
Shell extensions are loaded in almost every application you run (read : every application with a file open dialog or save or browse for folder…). If your shell extension is written in a .NET language (C#, VB.NET, but also Managed C++, C++/CLI) you simply inject the whole CLR in almost every application.
This has these consequences :
- In a managed program your shell extension could find itself to run under a different CLR version than expected. Unless your shell extension is CLR-1.0 it’ll probably fail to run.
- In a mixed mode program which loads a managed module in a second step (for instance a plugin) your shell extension could have forced a different CLR version to load and cause the application to fail.
- Visual Studio 2002 or 2003 could fail to debug an otherwise perfectly debuggable program if .NET Framework 2.0 or 3.0 is installed. This is because VS2002/3 fail to debug applications using CLR 2.0+ (you must use 2005), but it could get loaded because of your extension. You can use a manifest file to force CLR1.x to be loaded but it’s feasible only for your internal use, not for distribution.
So essentially, writing a shell extension in .NET is a good way to break applications and debuggers randomly.
It’s sad but UI in shell extensions must be written in p(l)ain C++.. 
:(
References :
- http://blogs.msdn.com/junfeng/archive/2005/11/18/494572.aspx
- http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=125283&SiteID=1
-
-
About
A blog about whatever gets on my computer or any other programmable device I own. From Linux to .NET.
Social Networking
-
Blogroll
- Ale+Ale - … Ale+Ale!
- Blog di Paolone (it) - (Italian) Il blog di un amico :)
- Bruce Eckel’s Free Electronic Books - Free Thinking in Java, C++, Patterns books. A must!
- Code Project - Free code snippets for Windows
- Dilbert - Where everyday work becomes comics
- Eriadan (it) - (Italian) IL blog a fumetti
- Freshmeat - Free (as in freedom) software for *nix systems
- Full Frontal Nerdity - A comic for nerds and alikes
- gotAPI - Language manuals and guides
- IlTucci (it) - Blog di un caro amico!
- Larry Osterman - Techblog of an experienced Microsoft developer
- Lightforce Games (Flash&JS)
- my del.icio.us page - my del.icio.us page
- Online virus scanning - Online virus scanning
- Order of the Stick - Best D&D Comic EVER!
- pinvoke.net - Wiki for P/INVOKE from .NET languages (C#, VB.NET)
- Programmers Heaven - Free programming resources
- ScriptSpot (3dsmax) - Free scripts for 3ds max
- Sourceforge - The biggest free (as in freedom) software library
- SpamUsement - Great site, where everyday spam becomes funny comics :)
- Sudoku di Repubblica (it) - Il sudoku di Repubblica! :)
- Tom’s Bug Blog - Brain teasers for programmers
