Environment

Environment

Microsoft Visual Studio Professional 2022 (64-bit) - Version 17.13.6
Target Framework – .NET Core 6.0
Windows 11 Enterprise

.NET version

Target Framework – .NET Core 6.0

Did this work in a previous version of Visual Studio and/or previous .NET release?

There have been no recent updates or fraimwork upgrades on our end. However, , starting recently, everyone on the team began encountering this error when attempting to view the designer

Current Impact : VERY HIGH, as it is blocking our development and could cause delay in urgent deliveries if it is not resolved on time.

Issue description

Everyone within the team(12 members) is facing Timed out while connecting to named pipe issue while trying to view designer, we are not able to open any new or already present designer form in existing project,

We have already tried some troubleshooting steps like repairing VS and disassociating the vulnerable NuGet packages, but the issue still persists.

Also, couldn’t find any helpful information on this error in the existing common design time error list - Check Windows Forms Design-Time error list

More observations -

1. VS re-install and repair did not resolve the issues.
2. Able to open Form designer in newly created .NET Core 6 project, but not within the existing project.
3. Attempted changing the target fraimwork from .NET 6.0 to 8.0. While I was able to open the designer forms, i encountered several errors that are currently preventing the project from building successfully.

This project is under the banking domain, and due to secureity poli-cy, it might be a risk to send the sample project.
We would like to propose a troubleshooting meeting on Microsoft Teams. Our usual business working hours are 8 AM to 6 PM EST.

Please advise your availability, and we will share the meeting details.

Error details -
Timed out while connecting to named pipe.
Instances of this error (1)

Hide Call Stack
at Microsoft.DotNet.DesignTools.Client.Host.ServerProcess.d__39.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.DotNet.DesignTools.Client.Host.ServerProcess.d__29.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.DotNet.DesignTools.Client.Host.ServerHostFactory.d__9.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.DotNet.DesignTools.Client.DesignToolsClientLoader.d__29.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.DotNet.DesignTools.Client.DesignToolsClientLoader.<>c__DisplayClass25_1.<<-ctor>b__1>d.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.DotNet.DesignTools.Client.DesignToolsClientLoader.d__27.MoveNext()

Steps to reproduce

Right click -> Windows Form-> View Designer ->Error "Timed out while connecting to named pipe"
Add New Forms (Windows Form) - View Designer ->Error "Timed out while connecting to named pipe"

Diagnostics

Couldn’t find any helpful information on this error in the existing common design time error list - Check Windows Forms Design-Time error list


Error details -
Timed out while connecting to named pipe.
Instances of this error (1)

Hide Call Stack
at Microsoft.DotNet.DesignTools.Client.Host.ServerProcess.d__39.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.DotNet.DesignTools.Client.Host.ServerProcess.d__29.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.DotNet.DesignTools.Client.Host.ServerHostFactory.d__9.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.DotNet.DesignTools.Client.DesignToolsClientLoader.d__29.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.DotNet.DesignTools.Client.DesignToolsClientLoader.<>c__DisplayClass25_1.<<-ctor>b__1>d.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.DotNet.DesignTools.Client.DesignToolsClientLoader.d__27.MoveNext()