Winforms designer still broken on every version since VS 16.4

We have had various updates on the winforms designer for net core but it keeps breaking or changing.

Using the ‘workaround’ on the following link did work on earlier versions of VS but is now no longer working with latest VS versions. https://github.com/dotnet/winforms/blob/master/Documentation/winforms-designer.md

Now broken again on VS ‘Version 16.6.0 Preview 5.0’ and ‘Version 16.5.4’

Please can someone give an update when this is likely to work? There has been very little feedback since December 2019 and I’m wondering whether to wait until May 2020 where it might work or abandon Winform netcore projects altogether.

Latest bug is as follows

Cannot find the requested resource: '207'.    
 
Instances of this error (1)  
 
1.   Hide Call Stack 
 
at Microsoft.VisualStudio.CommonIDE.ResourceLoader.TryEachApplicableNamespace[T](String resourceName, GetResourceDelegate`1 getResource)
at Microsoft.VisualStudio.CommonIDE.ResourceLoader.GetString(String resourceName, Int32 lcid)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at Microsoft.VisualStudio.LanguageServices.Implementation.ProjectSystem.InvisibleEditor..ctor(IServiceProvider serviceProvider, String filePath, IVsHierarchy hierarchyOpt, Boolean needsSave, Boolean needsUndoDisabled)
at Microsoft.VisualStudio.LanguageServices.Implementation.CodeModel.TextManagerAdapter.CreateTextPoint(FileCodeModel fileCodeModel, VirtualTreePoint point)
at Microsoft.VisualStudio.LanguageServices.Implementation.CodeModel.InternalElements.AbstractCodeElement.get_StartPoint()
at EnvDTE.CodeClass.get_StartPoint()
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.CodeTypeDeclarationFromCodeClass(CodeClass vsClass)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.OnNamespacePopulateTypes(Object sender, EventArgs e)
at System.CodeDom.CodeNamespace.get_Types()
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomParser.Parse(TextReader codeStream)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.MergedCodeDomParser.System.CodeDom.Compiler.ICodeParser.Parse(TextReader stream)
at System.CodeDom.Compiler.CodeDomProvider.Parse(TextReader codeStream)
at Microsoft.VisualStudio.Shell.Design.Serialization.CodeDom.Private.VSCodeDomDocDataAdapter.get_CompileUnit()
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.PerformLoad(IDesignerSerializationManager serializationManager)
at Microsoft.VisualStudio.Design.Serialization.CodeDom.VSCodeDomDesignerLoader.DeferredLoadHandler.Microsoft.VisualStudio.TextManager.Interop.IVsTextBufferDataEvents.OnLoadCompleted(Int32 fReload)  

[merriemcgaw]

I hope you all check out 16.7 Preview 1, lots of issues have begun to be ironed out. We’re bringing more features in for Preview 2 (and beyond of course). The only issue we’ve seen repeated mentions of recently is the ToolBox corruption which can be fixed by resetting your ToolBox or following more detailed instructions. Check out @OliaG’s blog post for details about what is in our current Previews and the comments for an alternative solution to the the ToolBox issue.

[merriemcgaw]

@kirsan31, somehow your ticket got routed incorrectly and didn’t hit my radar until now. @Shyam-Gupta and the team will take a look at what is happening. Now that we have the direct ticket link it’s on my radar and we’ll prioritize looking at it. Thanks so much for your patience!