Skip to content

Support MSBuildWorkspace.OpenProjectAsync() with file-based program #48708

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

Open
RikkiGibson opened this issue Apr 25, 2025 · 0 comments
Open
Labels
Area-run-file Items related to the "dotnet run <file>" effort untriaged Request triage from a team member

Comments

@RikkiGibson
Copy link
Member

RikkiGibson commented Apr 25, 2025

See also dotnet/roslyn#78303 (comment)

Eventually people will want to be able to use MSBuildWorkspace to load a file-based program. At minimum we probably want to add an OpenProjectAsync which takes both a project path and content, so, if the caller is able to put together a virtual project, they can make a workspace for it.

We may also want a new method that takes the FBP path itself and makes the virtual project and so on under the hood.

As part of this, batch builds need to be supported for in-memory projects using the Roslyn BuildHost APIs. See dotnet/roslyn#78303 (comment).

@dotnet-policy-service dotnet-policy-service bot added the untriaged Request triage from a team member label Apr 25, 2025
@jjonescz jjonescz added the Area-run-file Items related to the "dotnet run <file>" effort label Apr 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-run-file Items related to the "dotnet run <file>" effort untriaged Request triage from a team member
Projects
None yet
Development

No branches or pull requests

2 participants