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

Finish "project file editing" experience #4061

Closed
20 tasks done
davkean opened this issue Sep 28, 2018 · 10 comments
Closed
20 tasks done

Finish "project file editing" experience #4061

davkean opened this issue Sep 28, 2018 · 10 comments
Assignees
Labels
Feature-Project-File-Editing Editing the project either while open in Visual Studio, or via other mechanism. Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed.
Milestone

Comments

@davkean
Copy link
Member

davkean commented Sep 28, 2018

This is a tracking issue for finishing the project file editing:

Current State:

Find

If project file is closed:

If project file is open but not active:

If project file is open and active:

If AppDesigner is open

Open

Commands

Cleanup

Diff

@huoyaoyuan
Copy link
Member

Do you have plan for providing IntelliSense on project files?
When customizing my projects, I often need MSBuild reference to check exact spelling/meaning/value rule for properties. I also need reference when reading (not heavily) customized ones.
Currently, a vsix by Microsoft only provides quick information for nuget package reference.
This is not a trival work, so I want to know your choise on it.

@Pilchie
Copy link
Member

Pilchie commented Oct 29, 2018

This is something that's on our backlog, but right now we're focusing on:

  1. Performance and scale issues.
  2. Reliability issues in NuGet Restore, dependencies node, etc,
  3. Support for designers in order to support .NET Core 3.

So it's something we plan to do, but it will likely be a while before we have anything much to show for it.

@davkean
Copy link
Member Author

davkean commented Oct 30, 2018

@huoyaoyuan We do provide some IntelliSense:

image

Are you saying that you get none? If so, you might be running into dotnet/msbuild#2787.

@huoyaoyuan
Copy link
Member

Yes, I get none, even with xmlns added. And my VS is not in English too.

@davkean
Copy link
Member Author

davkean commented Oct 31, 2018

@huoyaoyuan Can you add information to dotnet/msbuild#2787 about the particulars of your OS language & VS language?

@davidwengier
Copy link
Contributor

Going to close this off as the work has been done, and PRs merged.

There is still #4215 outstanding however that is an existing issue, and #4222 still needs to be fixed, but they can be tracked individually.

@davidwengier davidwengier added the Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed. label Nov 5, 2018
@drewnoakes
Copy link
Member

See also #4325.

@cjbush
Copy link

cjbush commented Feb 8, 2019

Is there a way to disable double-clicking to edit for csproj files so that it can default to the regular behavior of expanding the node in Solution Explorer?

@davidwengier
Copy link
Contributor

It's coming with #4493

@cjbush
Copy link

cjbush commented Feb 8, 2019

Thanks! I missed that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature-Project-File-Editing Editing the project either while open in Visual Studio, or via other mechanism. Resolution-Fixed The bug has been fixed, refer to the milestone to see in which release it was fixed.
Projects
None yet
Development

No branches or pull requests

6 participants