A while ago, I started using the portable version of Paint.NET provided by this site. Before this, I was using a different portable Paint.NET which used the PortableApps Launcher, but was made by a third party.
One nice feature of this unofficial version is that it had the program's plugin folders (i.e. Effects and FileTypes) in the DATA folder. The PortableApps Launcher would then move these folders into Paint.NET's root folder when launching the program. There are two advantages of this approach:
1. The plugins are available for both the x86 and x64 versions of the program without having to make two copies of each one.
2. You're much less likely to have your plugins get deleted when installing an update.
Would it be possible to add this to add this feature to the official portable Paint.NET? Thanks.
Also, on a side note, would it be possible to change the app's name in the PortableApps Platform to "Paint.NET", instead of the current all lowercase name (paint.net). I personally think the former looks better. Thanks again.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
Do the 32-bit and 64-bit versions of paint.net work with all plugins? Usually apps have separate plugins for 32-bit vs 64-bit.
The Effects,FileTypes, Resources, and Shapes directories are preserved on upgrade for both the PaintDotNet and PaintDotNet64 directories, so you won't lose anything.
As for the titling, the app itself shows as paint.net now. I think the author transitioned over time away from the old Paint.NET titling.
Sometimes, the impossible can become possible, if you're awesome!
The plugins I've tried so far work with both 32 and 64-bit. Technically, the default method of compiling .NET EXEs and DLLs is in AnyCPU mode, which allows the code to run on any CPU that NET supports. The NET virtual machine will then take care of making the program's bytecode run on a particular CPU architecture. So the only way I see a Paint.NET plugin caring about bitness is if the author specifically compiled it with a specific architecture setting.
For the titling, I think I just realised why I prefer a capitalised name. It fits in better with the other portable apps this site has released. If you look at this screenshot of my PA Platform, you will see what I mean. Every program I have here, including the old 3rd party portable Paint.NET, has appropriate capitalisation in their names. But this site's Paint.NET, conversely, just has it in all lowercase and it sticks out.
https://imgur.com/x3Wan1d
You can right-click and rename the paint.net Portable to Paint.NET within the platform if you'd like it to match everything else.
As for plugins, I looked around a bit and it seems that the plugins work with both. Would you mind testing out a handful of the more popular plugin packs and verifying they work for both 32 and 64-bit for you? If so, I'll work on some custom code to import current sets into Data and handle it that way going forward.
Sometimes, the impossible can become possible, if you're awesome!
I'll see what I can do about the plugin testing.
"The best laid schemes o' mice an' men / Gang aft a-gley." - Robert Burns
I promise you nothing.