toe_head2001 Posted December 15, 2021 Share Posted December 15, 2021 With the recent version of paint.net, it seems the WinForms Designer can't open a form derived from EffectConfigDialog. In VS 2022, the "loading" message appears for infinity. However, VS 2019 is more informative, as it displays an actual error message: 1 Quote (September 25th, 2023) Sorry about any broken images in my posts. I am aware of the issue. My Gallery | My Plugin Pack Layman's Guide to CodeLab Link to comment Share on other sites More sharing options...
NinthDesertDude Posted December 15, 2021 Share Posted December 15, 2021 Fantastic, because I've been hand-editing and even inserting new elements in the generated .resx file and in the code-behind under InitializeComponent(). I thought it was just an artifact of the Try-Convert package on my repo. If there's more to it, I really hope it gets resolved. Quote Link to comment Share on other sites More sharing options...
toe_head2001 Posted December 15, 2021 Author Share Posted December 15, 2021 If I change the target to .NET 5, the designer loads up without issue. Switching back to .NET 6 causes the error to show again. This seems like a bug in .NET 6 rather than a bug in paint.net. So... target .NET 5 while WinForm designing, and then switch back to .NET 6. ¯\_(ツ)_/¯ Quote (September 25th, 2023) Sorry about any broken images in my posts. I am aware of the issue. My Gallery | My Plugin Pack Layman's Guide to CodeLab Link to comment Share on other sites More sharing options...
AndrewDavid Posted December 15, 2021 Share Posted December 15, 2021 Properly documented for @Rick Brewster Nice to see what I have been seeing for the past month. Didn't report it because I thought it was a VS thing. I may have mentioned it before. Build a new form based project in VS2022 without any references. I used the above to get it to link to Net 6.0 Without adding any code, add a blank form. Once you see it open properly, add references to Paint and then close the form. Try to open the form and watch the designer try to open. Then you receive this error Hopefully he can figure it out. Quote Link to comment Share on other sites More sharing options...
Ego Eram Reputo Posted April 15, 2022 Share Posted April 15, 2022 Anyone got a fix for the Designer not loading? Shift + F7 or Right-clicking EffectConfigDialog.CS > View Designer fails to load the designer with this error.... Timed out waiting for the design tools server process launch to complete. Quote ebook: Mastering Paint.NET | resources: Plugin Index | Stereogram Tut | proud supporter of Codelab plugins: EER's Plugin Pack | Planetoid | StickMan | WhichSymbol+ | Dr Scott's Markup Renderer | CSV Filetype | dwarf horde plugins: Plugin Browser | ShapeMaker Link to comment Share on other sites More sharing options...
otuncelli Posted April 15, 2022 Share Posted April 15, 2022 4 hours ago, Ego Eram Reputo said: Anyone got a fix for the Designer not loading? Shift + F7 or Right-clicking EffectConfigDialog.CS > View Designer fails to load the designer with this error.... Timed out waiting for the design tools server process launch to complete. I have a similar problem as well. This is another reason why I target .NET 5/Paint.NET 4.300. Failure has occurred while loading a type. Instances of this error (1) 1. Hide Call Stack at PaintDotNet.Runtime.CleanupManager..cctor() Error details in Windows Forms output (Paint.NET 4.3.10): [12:27:12.1992851] REQUEST FAILURES: Sessions/InitializeRootComponent Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: The type initializer for 'PaintDotNet.PdnBaseForm' threw an exception. ---> Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: The type initializer for 'PaintDotNet.Runtime.CleanupManager' threw an exception. ---> Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: Failure has occurred while loading a type. --- End of inner exception stack trace --- --- End of inner exception stack trace --- Quote Link to comment Share on other sites More sharing options...
otuncelli Posted April 16, 2022 Share Posted April 16, 2022 (edited) @Ego Eram Reputo @AndrewDavid Looks like the issue has been fixed in the latest Visual Studio 2022 (version 17.1.4). Edited April 16, 2022 by otuncelli 1 Quote Link to comment Share on other sites More sharing options...
AndrewDavid Posted April 16, 2022 Share Posted April 16, 2022 @otuncelli Updating to 17.2.1 to try again. I had 17.2 but don't remember trying anything form based. I Built about 50 Effect plugins for personal use and training. I'll try my tests for form based later tonight. Quote Link to comment Share on other sites More sharing options...
Ego Eram Reputo Posted April 16, 2022 Share Posted April 16, 2022 2 hours ago, otuncelli said: @Ego Eram Reputo @AndrewDavid Looks like the issue has been fixed in the latest Visual Studio 2022 (version 17.1.4). Thanks for this ^. I was using 17.1.1 - updating to 17.1.4 as I type. I'll report back on whether this solves the issue. ..nope Quote ebook: Mastering Paint.NET | resources: Plugin Index | Stereogram Tut | proud supporter of Codelab plugins: EER's Plugin Pack | Planetoid | StickMan | WhichSymbol+ | Dr Scott's Markup Renderer | CSV Filetype | dwarf horde plugins: Plugin Browser | ShapeMaker Link to comment Share on other sites More sharing options...
AndrewDavid Posted April 16, 2022 Share Posted April 16, 2022 21 hours ago, AndrewDavid said: I think we talked about the same issue here Well that issue has been resolved with my version of Studio. Now I can get back to trying to update an existing form based plugin to Net 6.0 Quote Link to comment Share on other sites More sharing options...
AndrewDavid Posted April 16, 2022 Share Posted April 16, 2022 @Rick Brewster After successfully building a plugin and seeing it function in Paint.Net, I go back to VS and try to open the form. I receive this error. Prior to building, the form worked fine. That allowed me to build it. The plugin is built on Net 5. Could that be the issue? Or is it an issue with Paint.Net? After changing the plugin to Net 6.0, I now get this reduced error when trying to open the form. I must be on the right track. The plugin still builds and will function in Paint.Net OK Issue resolved. Found an error in the plugin code. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted April 16, 2022 Share Posted April 16, 2022 I don't know. I never use the forms designer in Visual Studio, and none of Paint.NET's stuff is validated to work with it -- including the base EffectConfigDialog. Sorry. Someone else may be able to help or fix things. Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
toe_head2001 Posted August 15, 2022 Author Share Posted August 15, 2022 Anyone still having this issue? The designer had been working okay for a while, but now the issue is back. 🤔 I'm going to spend some time on this tonight, and see if I can solve it. Quote (September 25th, 2023) Sorry about any broken images in my posts. I am aware of the issue. My Gallery | My Plugin Pack Layman's Guide to CodeLab Link to comment Share on other sites More sharing options...
ReMake Posted August 15, 2022 Share Posted August 15, 2022 Yes, this issue exists for me. Visual Studio Community v17.3.0 Quote Link to comment Share on other sites More sharing options...
AndrewDavid Posted August 28, 2022 Share Posted August 28, 2022 Version 17.3.2 may have resolved the issue. Worked for my project that failed before. Quote Link to comment Share on other sites More sharing options...
Rick Brewster Posted August 28, 2022 Share Posted August 28, 2022 It'd also be worth trying Version 17.4 Preview Quote The Paint.NET Blog: https://blog.getpaint.net/ Donations are always appreciated! https://www.getpaint.net/donate.html Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.