Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The designer icon never appears in the Solution Explorer tab (the path spaces issue) #12978

Closed
Yaroslav-Kuznetsov opened this issue Feb 19, 2025 · 3 comments

Comments

@Yaroslav-Kuznetsov
Copy link

Yaroslav-Kuznetsov commented Feb 19, 2025

Environment

Visual Studio 17.13.0

.NET version

.NET 9

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

Yes

Issue description

Starting with the latest VS build it became impossible to show the visual designer, either by double clicking the file or using the context menu command. Note that the corresponding file association is still generated:

<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="Current" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
    <ItemGroup>
        <Compile Update="Form1.cs">
            <SubType>Form</SubType>
        </Compile>
    </ItemGroup>
</Project>

Image

Steps to reproduce

Create a brand new WinForms (.NET) project on any path that contains spaces in it. E.g.,
C:\Users\Admin\source\repos\New Folder (4)\WinFormsApp1\WinFormsApp1

Diagnostics


@Yaroslav-Kuznetsov Yaroslav-Kuznetsov added the untriaged The team needs to look at this issue in the next triage label Feb 19, 2025
@John-Qiao
Copy link
Member

A similar issue filed in design time: https://github.com/microsoft/winforms-designer/issues/6205

@Tanya-Solyanik
Copy link
Member

@Yaroslav-Kuznetsov - is this a duplicate of your issue - https://developercommunity.visualstudio.com/t/WinForms-designer-refuses-to-load-with-S/10754815, if it is then please upvote

@Shyam-Gupta
Copy link
Member

@Yaroslav-Kuznetsov This is a known issue and is under investigation. Here is a possible workaround for time being. Thanks.

@dotnet-policy-service dotnet-policy-service bot removed the untriaged The team needs to look at this issue in the next triage label Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants