I am trying to pull a dacpac from an existing database, importing it into a new SQL Project in VS2022 and then publishing it to another server.
I can sucessfully create and import the .dacpac and build the project. However, when I try to publish it via the right click Publish menu entry, I get several errors for unresolved dependencies:
[MyAssembly1] has an unresolved dependency to [System.Runtime.Remoting]. A deployment script with correct ordering cannot be created.
[System.Design] has an unresolved dependency to [System.Web]. A deployment script with correct ordering cannot be created.
[System.Runtime.Remoting] has an unresolved dependency to [System.Web]. A deployment script with correct ordering cannot be created.
[System.Web] has an unresolved dependency to [System.Design]. A deployment script with correct ordering cannot be created.
[MyAssembly2] has an unresolved dependency to [MyAssembly3]. A deployment script with correct ordering cannot be created.
[MyAssembly3] has an unresolved dependency to [System.Runtime.Remoting]. A deployment script with correct ordering cannot be created.
An error occured during deployment plan generation. Deployment cannot continue.
I included all named dependencies into my projects References (in fact they already existed in there). But I actually suspect, that this is not a problem of not finding the .dlls, rather than somehow messing up the dependency tree, since as you can see above [System.Web] depends on [System.Design] and vice versa, which seems highly unlikely to me, that there really are circular dependencies in NET Framework standard libraries.
Since the project includes many functions and stored procedures that rely on CLR Assemblies it is not really an option, to just strip the assemblies of the project, to get rid of the dependencies completely.