Publish always tries to find dacpac in .\bin\debug\

[dlaplante75]

Issue Type: Bug

right-click and publish a database. It will build but fail to deploy it if the tag is anything other than .\bin\debug\

In Azure Data Studio it fails without error messages. In VS Code is where you see the precise issue with the wrong path for the dacpac for deployment

Extension version: 0.17.1 Azure Data Studio version: azuredatastudio 1.37.0 (d904740d93d7df76a0ba361f20e4351813b57645, 2022-06-14T01:05:12.352Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No

System Info

|Item|Value| |---|---| |CPUs|Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz (8 x 2400)| |GPU Status|2d_canvas: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: enabled
opengl: enabled_on
rasterization: enabled
skia_renderer: enabled_on
video_decode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled| |Load (avg)|undefined| |Memory (System)|15.82GB (4.05GB free)| |Process Argv|| |Screen Reader|no| |VM|0%|

[kisantia]

@dlaplante75 where is the dacpac located when it's failing to publish? When building a project in ADS and vscode, the dacpac gets created in projectFolder\bin\debug

[dlaplante75]

@kisantia

If the projet file has a “….” tag, it will be located in wherever is written there. If there is no tag, it will be located in “bin\Output”.

In any case, the build is successful.

When the deployment starts, it systematically tries to get the dacpac from “bin\Debug”.

The only way to make it work is to specifically set the “….” tag to “bin\Debug”. Then it gets generated in the location where the publish expects it.

[kisantia]

Thanks for the additional details! I'll look into fixing this for the August release.

[JezWalters]

This problem is still occurring!

[kisantia]

@ssreerama fyi