vdproj Setup Project not generating .msi / .exe – System.Buffers.dll dependency warning (.NET Framework 4.7.2, x64)

Thank you for providing the detailed information.

This behavior is not related to your application configuration (x64 / .NET Framework 4.7.2), but instead indicates an issue with the Visual Studio Setup Project (.vdproj) dependency metadata itself.
This warning typically appears when the dependency information inside the .vdproj setup project becomes corrupted.

• Remove Setup Project from Solution In Solution Explorer, right‑click the Setup Project (.vdproj) and remove
• Re‑Add the Existing Setup Project Right‑click the Solution and select and Add to Existing Project as back into the solution.
• Re‑Link Primary Output After re‑adding, open the Setup Project and navigate to File System to Application Folder Remove the existing: Primary Output from <YourApp> Add it again using: Right Click and add it to project Output to primary Output.
• Clean and Rebuild build and clean solution and rebuild solution.

Above steps can help to resolve issue and Installer packaging stage will execute normally.
If solution is solved, please kindly accept the solution.

The warning text matches a known Visual Studio issue where deployment files for a Setup Project (.vdproj) become corrupted and the IDE reports:

Unable to update the dependencies of the project. The dependencies for the object 'name.dll' cannot be determined

In that state, the setup project can appear to build successfully but the deployment output is effectively broken.

Based on the available information, the questions can be addressed as follows:

1. The message “dependencies for the object 'System.Buffers.dll' cannot be determined” indicates the setup project’s dependency information has become corrupted. This is a known behavior when a solution contains both a Database Project and a Setup Project; the IDE can corrupt the deployment files after they are used multiple times.
2. Yes. Once the deployment files are corrupted, the setup project can no longer correctly resolve dependencies, which can prevent valid installer output from being produced even though the build is reported as succeeded.
3. The documented issue is not specific to .NET Framework 4.7.2 or x64, but to the Visual Studio 2005 IDE behavior with Web Setup/Setup projects when combined with a Database Project in the same solution. The symptom is the same dependency error you are seeing, so it is consistent with a limitation/bug in the setup project system rather than in System.Buffers.dll itself.
4. The recommended resolution from the documented issue is to avoid or correct the corrupted deployment files. In practice this typically involves:
   • Removing the problematic setup project from the solution and recreating it so that a fresh .vdproj is generated, and
   • Avoiding the solution configuration that triggers the corruption (for example, not combining the Database Project and Setup Project in the same solution, or rebuilding the setup project definition after such changes).

If the solution contains a Database Project alongside the Setup Project, separating them and recreating the setup project is the supported way to restore correct dependency resolution and allow .msi output to be generated again.

References:

• FIX: The Visual Studio 2005 IDE may corrupt the deployment files for a Web Setup Project and for a Setup Project