Visual Studio 2022 Version 17.4.3 kicks a**: mine
-
Thought I'd try out a simple WinForm/Core project: NET 7 standard 1 main form 1 usercontrol with a treeview and a panel built the solution without error dragged the usercontrol from the toolbos to the main form to create an instance: this error was reported: merry Xmas !
---------------------------
Microsoft Visual StudioFailed to create component 'HyperTree'. The error message follows:
'Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: The given assembly name or codebase was invalid. (0x80131047)
at Microsoft.DotNet.DesignTools.Client.DesignToolsClient.d__49`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()
at Microsoft.DotNet.DesignTools.Protocol.Endpoints.DesignToolsEndpoints.TypesImpl.FindType(String typeName)
at Microsoft.DotNet.DesignTools.Client.Types.ClientTypeIdentityResolutionService.FindType(String typeName)
at Microsoft.WinForms.DesignTools.Client.Toolbox.WinFormsToolboxItem.CreateComponentsCore(IDesignerHost host, IDictionary defaultValues)
at System.Drawing.Design.ToolboxItem.CreateComponents(IDesignerHost host, IDictionary defaultValues)
at Microsoft.DotNet.DesignTools.Client.Designers.ComponentProxyDesigner.CreateTool(ToolboxItem tool, Nullable`1 location, Nullable`1 size, ObjectProxy toolboxSnapArgs)'
OK
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
-
Thought I'd try out a simple WinForm/Core project: NET 7 standard 1 main form 1 usercontrol with a treeview and a panel built the solution without error dragged the usercontrol from the toolbos to the main form to create an instance: this error was reported: merry Xmas !
---------------------------
Microsoft Visual StudioFailed to create component 'HyperTree'. The error message follows:
'Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: The given assembly name or codebase was invalid. (0x80131047)
at Microsoft.DotNet.DesignTools.Client.DesignToolsClient.d__49`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()
at Microsoft.DotNet.DesignTools.Protocol.Endpoints.DesignToolsEndpoints.TypesImpl.FindType(String typeName)
at Microsoft.DotNet.DesignTools.Client.Types.ClientTypeIdentityResolutionService.FindType(String typeName)
at Microsoft.WinForms.DesignTools.Client.Toolbox.WinFormsToolboxItem.CreateComponentsCore(IDesignerHost host, IDictionary defaultValues)
at System.Drawing.Design.ToolboxItem.CreateComponents(IDesignerHost host, IDictionary defaultValues)
at Microsoft.DotNet.DesignTools.Client.Designers.ComponentProxyDesigner.CreateTool(ToolboxItem tool, Nullable`1 location, Nullable`1 size, ObjectProxy toolboxSnapArgs)'
OK
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
I use my VS 2022 professionally, to make my company shit tons of money. I don't have any issues with it or complaints. It definitely kicks ass!! Edit: apparently your issue is similar to issues people have had since 2005/2007 versions. the VS designer is not compatible with your version of HyperTree, or something like that. I am not entirely sure this is Microsoft's fault.
-
I use my VS 2022 professionally, to make my company shit tons of money. I don't have any issues with it or complaints. It definitely kicks ass!! Edit: apparently your issue is similar to issues people have had since 2005/2007 versions. the VS designer is not compatible with your version of HyperTree, or something like that. I am not entirely sure this is Microsoft's fault.
I definitely have issues with it and I have reported the bugs. One they claim is "behavior by design" and I disagree entirely. The other one they have acknowledged and it is repaired in the latest preview for v17.5. Both involve the Batch Build functionality which I use extensively because I have lots of solutions with multiple projects in them.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
I use my VS 2022 professionally, to make my company shit tons of money. I don't have any issues with it or complaints. It definitely kicks ass!! Edit: apparently your issue is similar to issues people have had since 2005/2007 versions. the VS designer is not compatible with your version of HyperTree, or something like that. I am not entirely sure this is Microsoft's fault.
HyperTree is a simple UserForm added to the Project the standard way via menu. I believe this blow to my gluteus maximus may have been caused by demonic entities ... they are attracted to situations like this because the smell of the assumption that things will go "right," is like an aphrodisiac.
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
-
Thought I'd try out a simple WinForm/Core project: NET 7 standard 1 main form 1 usercontrol with a treeview and a panel built the solution without error dragged the usercontrol from the toolbos to the main form to create an instance: this error was reported: merry Xmas !
---------------------------
Microsoft Visual StudioFailed to create component 'HyperTree'. The error message follows:
'Microsoft.DotNet.DesignTools.Client.DesignToolsServerException: The given assembly name or codebase was invalid. (0x80131047)
at Microsoft.DotNet.DesignTools.Client.DesignToolsClient.d__49`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.JoinableTask.CompleteOnCurrentThread()
at Microsoft.VisualStudio.Threading.JoinableTask`1.CompleteOnCurrentThread()
at Microsoft.DotNet.DesignTools.Protocol.Endpoints.DesignToolsEndpoints.TypesImpl.FindType(String typeName)
at Microsoft.DotNet.DesignTools.Client.Types.ClientTypeIdentityResolutionService.FindType(String typeName)
at Microsoft.WinForms.DesignTools.Client.Toolbox.WinFormsToolboxItem.CreateComponentsCore(IDesignerHost host, IDictionary defaultValues)
at System.Drawing.Design.ToolboxItem.CreateComponents(IDesignerHost host, IDictionary defaultValues)
at Microsoft.DotNet.DesignTools.Client.Designers.ComponentProxyDesigner.CreateTool(ToolboxItem tool, Nullable`1 location, Nullable`1 size, ObjectProxy toolboxSnapArgs)'
OK
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
Quote:
Thought I'd try out a simple WinForm/Core project: NET 7 standard
Why? ;)
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain -
Quote:
Thought I'd try out a simple WinForm/Core project: NET 7 standard
Why? ;)
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domainbecause i can't get over Santa's beard :wtf:
«The mind is not a vessel to be filled but a fire to be kindled» Plutarch
-
Quote:
Thought I'd try out a simple WinForm/Core project: NET 7 standard
Why? ;)
Latest Article:
Create a Digital Ocean Droplet for .NET Core Web API with a real SSL Certificate on a Domain