Zi Chen

If I create a project directly from database, the login is there.

If I create a project directly from database and select "File" as the extract target, everything works there.

There are a few compatibility issues with packages generated from .NET Core and the .NET Framework version of DacFx. The recommendation is to use the same version for both import/export....

@Ri7Sh In #443 you have `CoreCompile` overridden. Do you think the proposed changes will work with SSDT?

The only new Import we added in 0.1.15-preview is to Microsoft.NET.Sdk.targets, which shouldn't be empty either https://github.com/microsoft/DacFx/blame/a888164f1e83f0b64f130875600d90205adb7c23/src/Microsoft.Build.Sql/sdk/Sdk.targets#L50

I believe this exact error is fixed by https://github.com/dotnet/sdk/pull/30091 That property `ILLinkTargetsPath` should be set during restore, but in some cases it seems to leave it blank. The fix above...

That target was introduced in .NET 7 so it's not in the .NET 6 SDK, but the fix isn't in the latest .NET 7 patch.

Does running an explicit `dotnet restore` before build solve the issue? I'm not sure if there is any fix besides asking the dotnet team to port the change to .net...

It is to support transitive project references for sqlproj. If A references B and B references C, A should now understand C's objects.

We just released 3 system dacpac Nuget packages that can be referenced via `PackageReference` from projects built with Microsoft.Build.Sql 0.1.9-preview and up. Example: ```xml ``` Available packages are: * [Microsoft.SqlServer.Dacpacs](https://www.nuget.org/packages/Microsoft.SqlServer.Dacpacs)...