This issue is repeated many times on the web, but I have not found any solutions that covers my problem. Copy all code from the old class library to the new. In the Win Form project: Replace the reference to the old class library with the new.
I have no cross-solution references or reference to missing projects. If I remove the reference to the class library, the error disappear. We have already fixed this problem in Visual Studio 2010.
I have isolated the problem in a solution with just a setup project, a Win Form project and a class library. No error occours if I replace the class library with a newly created one, so it looks like there are something wrong with my class library project. We encourage you to try out our Visual Studio 2010 RC release which can be obtained from
Error 0x80070570 Failed to extract all files from container. The account for Poly Base Engine service is not allowed.
SQL Server Management Studio 2016 (SSMS 2016) failed to install, e000: Error 0x80070570: Failed to extract all files from container, erf: 1:4:0. The specified account for SQL Server Poly Base Engine (same error for Poly Base Data Movement) service is not allowed.
The prerequisites are not installed: Visual Studio 2010 Tools for Office Runtime. Trying to upload a Report Model on the Web portal of SQL Server 2016 Reporting Services resulted on the error 'Feature not supported'.
Error installing Microsoft SQL Server 2016 MDS Add-in for Excel.
From the attached project, the project “Windows Form Application1” in Solution2 references a project that is not in Solution2 (it references Class Library1 from Solution1).
To fix the error, the workaround is to copy the Class Library1 project to Solution2 and re-add the reference to Class Library1 within its own solution.Error installing Microsoft Visual C 2015 Redistributable. Cannot connect to SQL Server after installing SSMS 2016 july Update. Warning Setup Limited to Reporting Services for Share Point. VS Shell installation has failed with exit code 1638. Unable to install database engine on SQL Server 2016, only Reporting Services (Share Point) and Reporting Services Add-in for Share Point products are allowed to install. Microsoft SQL Server Management Studio: Could not load schema model from package. Solution2Setup This actually works fine when building the solutions from the IDE.But, there is some kind of dependency computation problem when trying to create Setups for each solution.Perhaps you could modify my attachment then send it back to me so that I can understand what you are trying to say. We were able to reproduce the problem and have identified the root cause.