Add predefined variable ${fileDirBasename}

[kzhui125]

Hello, I have some dotnet solutions opened as my root workspace.

For example:

${workspaceFolder}:
/home/username/dotnet-solution1

${file}:
/home/username/dotnet-solution1/project1/Program.cs
/home/username/dotnet-solution1/project2/Program.cs
/home/username/dotnet-solution1/project3/Program.cs
/home/username/dotnet-solution1/project4/Program.cs

When I open Program.cs or other cs file, I want press F5 to debug the corresponding project.

So I need this ${fileDirBasename} variable.

this is my expected lanunch config:

{
    "name": "Launch current project",
    "type": "coreclr",
    "request": "launch",
    "preLaunchTask": "build",
    "program": "${fileDirname}/bin/Debug/netcoreapp2.0/${fileDirBasename}.dll",
    "args": [],
    "cwd": "${fileDirname}",
    "stopAtEntry": false,
    "console": "internalConsole"
}

my expected build task:

{
    "label": "build",
    "command": "dotnet",
    "type": "process",
    "args": [
        "build",
        "${fileDirname}/${fileDirBasename}.csproj",
        "/property:GenerateFullPaths=true",
        "/consoleloggerparameters:NoSummary"
    ],
    "problemMatcher": "$msCompile"
}

[isidorn]

/findDuplicates

[isidorn]

There might be already a feature request for this, unfortunetly I can not find it.
Leaving it open as a feature request for now and assigning to @alexr00

[rioj7]

for this project directory structure what is this variable different than ${relativeFileDirname}?

[kzhui125]

@rioj7

consider this example:

/home/username/dotnet-solution1/dir1/project1/Program.cs

${relativeFileDirname} will be dir1/project1, I won't get "${fileDirname}/${fileDirBasename}.csproj" using ${relativeFileDirname}

[rioj7]

@kzhui125 I have added this variable to the extension Command Variable v0.7.0.

In case you have a project structure

/home/username/dotnet-solution1/dir1/project1/Program.cs
/home/username/dotnet-solution1/dir1/project1/subdir1/tool.cs

And if your current file is tool.cs the launch or build will go bad.

Then you should use extension.commandvariable.file.fileAsKey

{
  "version": "2.0.0",
  "tasks": [
    {
        "label": "build",
        "command": "dotnet",
        "type": "process",
        "args": [
            "build",
            "${input:chooseFileBasename}/${input:chooseFileBasename}.csproj",
            "/property:GenerateFullPaths=true",
            "/consoleloggerparameters:NoSummary"
        ],
        "problemMatcher": "$msCompile"
    }
  ],
  "inputs": [
    {
      "id": "chooseFileBasename",
      "type": "command",
      "command": "extension.commandvariable.file.fileAsKey",
      "args": {
        "/project1/": "project1",
        "/project2/": "project2"
      }
    }
  ]
}

You need to make the key as specific as needed.

[alexr00]

Could you do ${fileDirname}/${relativeFileDirname}/${fileBasenameNoExtension}.csproj?

[kzhui125]

@rioj7 thanks, I will have a try.

@alexr00

for example:
/Users/test/Documents/dotnet-solution1 opened as ${workspaceFolder}:
/Users/test/Documents/dotnet-solution1/dir1/project1/Program.cs opend as ${file}

my expected launch.json:

/Users/test/Documents/dotnet-solution1/dir1/project1/bin/Debug/netcoreapp2.0/project1.dll

my expected tasks.json:

/Users/test/Documents/dotnet-solution1/dir1/project1/project1.csproj

${fileDirname} will be /Users/test/Documents/dotnet-solution1/dir1/project1
${relativeFileDirname} will be dir1/project1
${fileBasenameNoExtension}.csproj will be Program.csproj

so ${fileDirname}/${relativeFileDirname}/${fileBasenameNoExtension}.csproj will be:

/Users/test/Documents/dotnet-solution1/dir1/project1/dir1/project1/Program.csproj

It's not as expected.

[alexr00]

${workspaceFolder}/${relativeFileDirname}/${fileBasenameNoExtension}.csproj?

[kzhui125]

@alexr00

${fileBasenameNoExtension}.csproj will be Program.csproj

But project1.csproj is expected

[alexr00]

Ok. The feature request here is for a variable the resolves to the second to last segment of the current file's path.

[alexr00]

The new variable is fileDirnameBasename

[github-actions]

Unable to locate closing commit in issue timeline. You can manually reference a commit by commenting \closedWith someCommitSha.

[alexr00]

\closedWith 551db7e

[github-actions]

This bug has been fixed in to the latest release of VS Code Insiders!

@kzhui125, you can help us out by confirming things are working as expected in the latest Insiders release. If things look good, please leave a comment with the text /verified to let us know. If not, please ensure you're on version 0a80aac of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.

Happy Coding!

[aeschli]

Verified with

{
    "version": "2.0.0",
    "tasks": [
        {
            "label": "echo",
            "type": "shell",
            "command": "echo",
            "args": ["${fileDirnameBasename}"],
            "problemMatcher": []
        }
    ]
}