Preflight Checklist
Power Query SDK
0.3.1
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
No response
VSCode version
No response
PQSdkTool Path
No response
Bug Description
In my .vscode/settings.json I have changed the name for the mez file:
"powerquery.sdk.defaultExtension": "${workspaceFolder}\\bin\\AnyCPU\\Debug\\NotSameNameAsDirectory.mez",
I have also changed my .proj file PropertyGroup
<PropertyGroup>
<OutputPath Condition="'$(OutputPath)' == ''">$(MSBuildProjectDirectory)\bin\AnyCPU\Debug\</OutputPath>
<IntermediateOutputPath Condition="'$(IntermediateOutputPath)' == ''">$(MSBuildProjectDirectory)\obj\</IntermediateOutputPath>
<MezIntermediatePath>$(IntermediateOutputPath)MEZ\</MezIntermediatePath>
<MezOutputPath>$(OutputPath)NotSameAsDirectory.mez</MezOutputPath>
</PropertyGroup>
However, when I run the build task MakePBX the generated mez file name is the parent directories name.
Steps to Reproduce
- Create new extension project, in a folder called
bug-folder
- update the
.vscode/settings.json to have a new mez file name, CoolName.mez
- update the
.proj file and change the MezOutputPath to also have the CoolName.mez
Actual Experience
bug-folder.mez is created instead of CoolName.mez
Expected Experience
No response
Additional Context
No response
Preflight Checklist
Power Query SDK
0.3.1
Regression From
No response
Platform
Windows
Architecture
x64
OS Version
No response
VSCode version
No response
PQSdkTool Path
No response
Bug Description
In my
.vscode/settings.jsonI have changed the name for themezfile:I have also changed my
.projfilePropertyGroupHowever, when I run the build task
MakePBXthe generated mez file name is the parent directories name.Steps to Reproduce
bug-folder.vscode/settings.jsonto have a new mez file name,CoolName.mez.projfile and change theMezOutputPathto also have theCoolName.mezActual Experience
bug-folder.mezis created instead ofCoolName.mezExpected Experience
No response
Additional Context
No response