AndrewDavid

It is.

@Rick Brewster OK - back in business. Current Beta installed. Secondpdn.zip This trace is after opening Paint the second time. Attempting to do a trace the first time (after reboot) causes the app to hang (Program not responding). Closed through task manager this time. Because it wasn't shut down through exit - it won't record the trace. Just a corrupted file is found. 5 minutes of hanging was too long.

@Rick Brewster Now I am having big trouble getting paint to run. I was using it all morning (at least 2 hours). When you asked for the trace, I rebooted to get a fresh start. After searching for the trace command, I had trouble getting it to work. It finally took - started paint, but all I saw was the little blue circle, and the app not responding message. I was able to close it clicking on the X button. Got the normal program not responding/report to Microsoft message and cancelled out back to the desktop. Rebooted - Tried to restart paint - no luck - just the blue circle after clicking on effects. Uninstalled and installed previous beta version - still no luck - just the blue circle after clicking on effects. Now I have uninstalled that version and debating what to do next. I do recall having trouble getting that trace to work. I know its just a switch and shouldn't damage the installation, but something corrupted something. I'll do a SFC and get back to you.

@Rick Brewster Somethings wrong pdn.zip

@Rick Brewster Almost missed this update - so wrapped up in the template walkthrough. After updating - I can attest to the speedier loading of the plugins. Doc loading is faster too

The plugin index will take you to the first page that shows the old version as 4.3 has not been released. You need this version https://forums.getpaint.net/topic/110458-the-plugin-browser-v1310-april-28-2020/page/6/?tab=comments#comment-585131 which you will find at the end of the thread. Version 1.3.9.2 is what you are looking for.

@Rick Brewster Well done on the fixes. "I can barely see anything in that screenshot/picture" My upload size is limited. No big pictures. 😊

As I am seeing. Little things create big problems. Programming is no easy task.

Confirmed

Here I have problem with a simple solution you can find I'm sure. I decompiled a small outdated plugin AdvGrey.dll to try and build it in VS2022 Preview Net 5.0 from the beginning. One error has stumped me in the code. The only error I get is for the underlined IsVisible extension method found at line 67 Its such a small plugin, I don't know how it could stump me. The code is contained in the old DLL and works fine in Paint.net. Upgrading it to Net 5.0 showed what has been depreciated and I was able to fix all errors except this one. Could you please help?

@Rick Brewster Open any image Reduce transparency to 50% by Adjustments/Transparency (Boltbait's plugin) Set brush size to 20 /100% Hardness Color Black 0,0,0,255 See what happens; 2 things outside 20 diameter maybe 90% erasure. quick fix I'm sure

@toe_head2001 thanks for having a look. More lessons learned Anything else I can chew?

Hi Martin I've been a fan of your plugins for awhile and just realized the name change. For your info, I'm starting to learn how to use VS2019 to create plugins. Create is not really the right word, recover would be better. I have the beta version of Paint.net installed and working on modifying some old plugins to learn VS. Your PdnPropertiesAndControls provided me with a valuable learning experience that I used to rebuild your plugin. I hope you don't mind my posting to GitHub for reference purposes. https://github.com/AndrewDavid007/PdnPropertiesAndControlTypes. It's too bad not every plugin is in GitHub.

It does say create addons and extensions (which I have no plans on doing) which is why it wasn't installed. Once installed, still no config manager. I'll just continue downloading until I get it. I have time to learn. Do you see it? I may have to build it as a custom tool.

Configuration Manager in Visual Studio 2019? I attempted to make the changes in the previous post to update the template for Core 5.0. No easy task. I tried editing the code with Visual Studio Code but when I opened the Project in Visual Studio it prompted me to open the Configuration Manager. Microsoft Docs describes how to activate Configuration Manager but my installation is missing the described menu entry. "Show advanced build configurations" does not exist. I did try another approach by building the template from a new project, but when copying the code into the new project, there were too many errors generated (not because of lack of references). Seems Core 5.0 is a whole new language.

@Rick Brewster I would like to go back to the list of broken plugins and remove all the lines over plugins that are still not operating at 100%. When and if you release the next update, users will need to know what no longer works. I can think of 3 categories. 1. Broken - Will not load/crashes Paint.Net. 2. Fixed - Will run but at reduced capability/new version may or may not needs to be downloaded. (Like CircularText) 3. Fixed to full functionality/Download required. (Like Plugin Browser). Red/Yellow\Green markers. Maybe the text if the software will allow, Thoughts?

CircularText.DLL Uploaded another broken plugin to GitHub. This is one that would not load in the new beta version. It loads fine now but still has the menu problem. Different error as well. It will load but not save. That ball is in your court. The headache of updating software. The plugin still works, just lost some of its functionality.

Hi @Echo Welcome to the Forum Another suggestion https://forums.getpaint.net/topic/108312-trs-monolithic-3d-text-generator-feb-26-2019/?ct=1630138324 Let us know which one you choose.

https://forums.getpaint.net/topic/111330-unfinished-plugins/page/6/ After building JustifyText I see no problem using ILSpy.exe. I didn't need any assistance for that one. (After finding a message you wrote along time ago). At least that's one app I understand. I'll try your suggestion and see if its any better. I think these plugins were built in codelab. Decompiling them for Visual Studio is the challenge.

Buried in Unfinished plugins ILSpy.exe

@Rick Brewster @toe_head2001 JusttifyText.DLL Uploaded another broken plugin to GitHub for determining what is causing the failure of the plugin's menu attempt to save/load files. Definitely need help for this one. I can't even find the source code for that functionality. I have been able to create the DLL correctly, I have updated it to run on net5.0-windows and hope you can resolve this loss of functionality. There are about six more plugins that fail in the same manner, so I hope when we determine the correct code for this one, it can be applied to the others. This is the error

I was able to build the dll so I don't think it's an issue anymore.

CustomFrame.DLL There was a resource file under selectframe.cs / (I deleted it too but I think I still need it) Followed your suggestion and found the resource file the decompiler created. I must of added it to selectframe.cs in error (I do make mistakes) I learned there is a big difference between copying and pasting and or Add new/existing item to a project. And now the good news It successfully built the dll that now runs in Paint.net It doesn't do what the old plugin did so I'm not out of the woods yet. From what I remember, you could open a premade png file to create the custom frame. Although working, it doesn't give that option. I've pushed the changes to GitHub and await your thoughts on this matter. This is where Selectframe.cs comes in. I think that was the functionality it provided.

Another challenge for you. Does this look like something you can figure out? Could it be a bug in Visual Studio? I'm adept at generating error messages

@midora Thanks for the help. Overnight @toe_head2001 made a few changes and I just added another one to GitHub. When you say "build it" do you mean build the project file? The current issue is trying to get the dll to work. Have you been able to successfully debug it? The current error I am getting is; That's where I am stuck. When debugging, it gives that error on line 18 of EffectPlugin.cs I didn't think rebuilding an old plugin would be so difficult. But it is a good learning experience. Any help you can provide in debugging this would be greatly appreciated. No reason why you can't join us on GitHub as well.