8000 [SUGGESTION] Expose the current solution path as a VSCode variable that can be used in tasks.json · Issue #2031 · microsoft/vscode-dotnettools · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

[SUGGESTION] Expose the current solution path as a VSCode variable that can be used in tasks.json #2031

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.

Sign up for GitHub

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

Jump to bottom
Open
sebwills opened this issue May 21, 2025 · 0 comments
Open

[SUGGESTION] Expose the current solution path as a VSCode variable that can be used in tasks.json #2031

sebwills opened this issue May 21, 2025 · 0 comments
Labels
area-vscode enhancement New feature or request

Comments

@sebwills
Copy link

Describe the feature you'd like

I use an explicit dotnet build command defined in tasks.json to build, because I need to customize the build parameters (see #1362).

e.g.

{
            "label": "build",
            "command": "dotnet",
            "type": "process",
            "args": [
                "build",
                "--no-restore",
                "${workspaceFolder}/path/to/my/solution.sln",
...

Currently I have to explicitly provide the path to my .sln file, and I have to manually update the path in tasks.json (or create a different build task) every time I change solution within same workspace.

I would like the path to the currently open solution file to be exposed as a variable that can be used in tasks.json (https://code.visualstudio.com/docs/reference/variables-reference)

Alternatives considered

No response

Environment Information

No response
@sebwills sebwills added the enhancement New feature or request label May 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-vscode enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sebwills @phil-allen-msft
0