Code alignment 3, Wine1.4: unknown exception

Code alignment v3.0 on Linux Mint 10, based on Ubuntu Maverick, under Wine 1.4.0 causes unknown exception when starting N++. N++ will start but crashes soon after opening Plugin Manager, most likely due to missing .NET 3.5.

By what fucking excuse you think .NET is worth anything ? All it does it corrupt and prevent cross-platform support. Either quit or switch language, or help making .NET compatible !! Oh, I forgot ! Micro$oft dicks can't help !! FUCK YOU.

Thank you for reporting the bug with Plugin Manager. Usually people develop with languages they are comfortable with. I don't know myself what language and version (if any) of the .net framework that Plugin Manager requires. If you would like to fork the project and fix this then you are welcome. I happen to know that some people really love Linq (I've never used it). If you want to mention your disapproval of this in such a colourful way, there is a separate forum for that: "Boycott Notepad++ here". Of course, if you don't like NPP then you can use a wide selection of similar tools. For linux, I quite like gEdit.

AFAIK, Plugin Manager doesn't contain any .NET component, and it's written C++ as well.
Plugin Manager is one of the most stable and useful plugins for Notepad++. That's the reason that it is always included in the official release. The author wrote it with his free time and offers it as free (open source). It's unfair to blame him for not working  under WINE, which is not even supported officially by Notepad++.

BTW, I'm kind of surprised you have a computer: The way you talk makes me think that you come from cave.

Don

Wasn't it about Code Alignment 3.0 - and not about Plugin Manager?

Just to clear this up (not for the original troll, but for anyone else finding this thread) - plugin manager is indeed written entirely in native C++, without any MFC, just as Notepad++ itself is.  In order to identify the plugins installed it calls the same methods that notepad++ itself calls (getPluginName() etc).   Unfortunately, some plugins wrongly expect that when they are loaded (with LoadLibrary()), they are being loaded by Notepad++ itself, and therefore will expect that all the notepad++ functions are called in order (setInfo() etc).  What this then means is that the plugin DLL is unloaded (with FreeLibrary()), before the plugin expects it, and can, for a badly behaved plugin, cause a crash.

This problem will show itself every now and again (specifically when the automatic check for plugin updates is done), and when the user opens the plugin manager window (or shortly after).  I would imagine the way WINE deals with loading and unloading DLLs may have an effect on how stable N++ is after such an occurance.  It could also have difficulty with mixed-mode assemblies (.NET and native together in one DLL).   I have no WINE test environment, and as Done mentioned, it's not officially supported - testing the plugin install correctly takes long enough as it is without doubling the test environments.

If the problem only manifests itself under Wine, you're probably out of luck - if not, then hopefully the Code Alignment author can take a look.

Cheers,
Dave.

I know I'm responding to a troll but I'll bite.
I bet if somebody gives you a free chocolate ice cream you tell them to fuck off because it wasn't strawberry.

Let's get this clear, code alignment is a free extension. I've released purely out of the good of my heart.

I have no responsibility to make you happy and I owe you nothing. Yet you come on here and act like you're entitled to use it. That I have somehow wronged you.

I wrote this extension to help myself, since then I have added requests for others which have no value to me. But if you think I'm going to waste my time to satisfy a low life who can't even be bothered to treat me with respect, you're delusional. Write it yourself.

If i did make it wine compatible i bet you would tell me to fuck off as i hadn't written a port for eclipse yet.

The main reason I wrote it in .net is because it's a port of my extension for visual studio. Keeping it in .net let me share the code, develop it faster and not have to maintain duplicate code. Giving me more time to add new features and spend doing other things.

Grow up.