Zi Chen

> Ok here is the behavior I'm observing. I think the parsing of pre/post-deployment scripts is supposed to happen, we have some 72xxx error codes that are specific for pre/post...

@llali no I recall working on this and verifying that it's reproducible, but don't think a fix was implemented yet.

Hi @ben-purcell thank you for opening this issue. Right now SDK-style database projects are only supported on the 'SQL Database Projects' extension in Azure Data Studio or VS Code. Support...

Looks like there's an issue with the DotNetCoreCLI task, it's ignoring the flag and only running tests for .NET 6. I submitted an issue: https://github.com/microsoft/azure-pipelines-tasks/issues/17078

Because of that issue I'm changing it so it defaults to multi-target, can be overridden like this `dotnet test -f net6.0`

nuget.org should be included by default. @PowerDBAKlaas do you have any additional Nuget sources configured? You can run `dotnet nuget list source` to check.

I believe this is the line of code in question: https://github.com/microsoft/SqlScriptDOM/blob/4b7e0af48237191f14612855acda32c97470fe02/SqlScriptDom/ScriptDom/SqlServer/SqlScriptGenerator.cs#L116

I don't think this is a DacFx issue. Those views aren't correctly marked as `is_ms_shipped` in `sys.all_views`. @salilkanade can you update/close this issue once you verify with the engine team?

Feel free to reopen if some specific logic is required in DacFx to exclude them.

If I create a project directly from database, or extract using sqlpackage, the objects are created properly. Distinct files are created for each object