I am having an issue rebuilding a multi-project solution that contains an installer project. I keep getting the error: ERROR: Unrecoverable build error
I have scoured Google and this site and have tried the following, with no success;
Repairing VS
Repairing SSDT
Uninstalling SSDT
Registering both mergemod.dll and ole32.dll after closing VS and then rebuilding
If anyone has not been able to solve this issue using the above methods, I'd love to hear about it!
Thanks!
I had a similar issue yesterday (but with VS 2008). I did the following 3 steps and it fixed the issue:
Register the DLL mergemod.dll (regsvr32.exe C:\Program Files (x86)\Common Files\Microsoft Shared\MSI Tools\mergemod.dll)
Register the DLL ole32.dll (regsvr32.exe ole32.dll)
Delete the cache/temporary visual studio files – which get generated as part of the builds. (C:\users{BUILD_USER}\appdata\local\temp).
Hope that helps!
Related
I've run in to an issue where I can't build a freshly created C++/CLI Class Library project in Visual Studio:
Even though I haven't made any changes I get an error when I try to compile:
Severity Code Description Project File Line Suppression State
Error Could not load UI satellite dll 'FileTracker32UI.dll'. Make
sure it exists in an LCID subdirectory of 'C:\Program Files
(x86)\MSBuild\14.0\bin\'. TestProject c:\Users\abcde\documents\visual
studio 2015\Projects\TestProject\TestProject\FileTracker 1
I've created C++/CLI Class Library projects in the past on the same computer using Visual Studio 2015 without encountering this problem. Any idea what has gone wrong?
I ran into this strange issue today without making any code change. I suspect it appeared due to overnight windows update.
In my case , I copied the two files FileTracker32UI.dll and FileTracker64UI.dll
From
C:\Program Files (x86)\MSBuild\15.0\FileTracker\3082\
To
C:\Program Files (x86)\MSBuild\14.0\Bin\3082\
and it worked. My visual studio version is
Microsoft Visual Studio Community 2015
Version 14.0.25123.00 Update 2
I am hoping the info helps someone.
I had the exactly same problem, after some windows update by my IT.
According to the information (https://forum.dlang.org/post/ezuohezwuzyitjdzpfdw#forum.dlang.org), I renamed the file "FileTrackerUI.dll" to "FileTracker32UI.dll" in the latest LCID folder (latest numbered folder in same location)
Then, it worked at my PC.
Good luck
In my case it was a path issue. Using another directory (shorter path without special characters) solved the problem
I am having issues porting visual Studio Express solutions over to Visual Studio 2017. I have attempted to follow the advice in this article which has not solved the issue.
When I load my solution in 2017, I get an error stating "one or more projects in the solution were not loaded correctly" with the following output:
C:\Users\mikegjohn\Documents\Service Hub\Service_Hub\WindowsApplication1\Service_Hub.vbproj : error : The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\Microsoft\VisualStudio\v15.0\SSDT\Microsoft.Data.Tools.Schema.Sql.UnitTesting.targets" was not found. Also, tried to find "Microsoft\VisualStudio\v15.0\SSDT\Microsoft.Data.Tools.Schema.Sql.UnitTesting.targets" in the fallback search path(s) for $(MSBuildExtensionsPath32) - "C:\Program Files (x86)\MSBuild" . These search paths are defined in "C:\Users\mikegjohn\AppData\Local\Microsoft\VisualStudio\15.0_825df01c\devenv.exe.config". Confirm that the path in the declaration is correct, and that the file exists on disk in one of the search paths. C:\Users\mikegjohn\Documents\Service Hub\Service_Hub\WindowsApplication1\Service_Hub.vbproj
My solution explorer shows nothing and i cannot view any of the properties.
Can anyone point me in the right direction?
I managed to fix this with the help of Lex Li Jun. I reinstalled a number of SQL modules which were left out on the standard VS2017 package and this solved my problem!
We made the switch to Visual Studio 2017 and having trouble with our self-hosted build agent that gets its work from VSTS.
One VSTS-build step is building all solutions with "Visual Studio Build: Build Solution ***.sln" using "Visual Studio Version: Visual Studio 2017".
The following error happens for all our projects where "ASP.NET Core Web Application (.NET Core)" was the chosen project type.
C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0\TransformTargets\Microsoft.NET.Sdk.Publish.TransformFiles.targets(54,5): error MSB4062: The "TransformWebConfig" task could not be loaded from the assembly C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks\Microsoft.NET.Sdk.Publish\build\netstandard1.0....\tools\net46\Microsoft.NET.Sdk.Publish.Tasks.dll. Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks\Microsoft.NET.Sdk.Publish\tools\net46\Microsoft.NET.Sdk.Publish.Tasks.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format. Confirm that the declaration is correct, that the assembly and all its dependencies are available, and that the task contains a public class that implements Microsoft.Build.Framework.ITask.
Additional information:
From within Visual Studio 2017 the solutions built without any errors.
None of our projects include any .config transformations files (but do include .config files like web.config), still the error occurs.
Visual Studio 2017 Build Tools as well as full Visual Studio 2017 have been installed on the build server and e.g. .NET Core Class Libraries compile fine.
Installed .NET Core versions are identical between build server and developer machines.
The same errors also happen when using "MsBuild: Build Solution ***.sln" as a build step for all solutions and selecting "MSBuild: MSBuild 15.0".
The file mentioned as "Could not load file or assembly: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\MSBuild\Sdks\Microsoft.NET.Sdk.Publish\tools\net46\Microsoft.NET.Sdk.Publish.Tasks.dll" does exist in the mentioned path.
No tasks are defined within the .csproj files.
Anyone got any insight as to what might cause this?
Have a look below:
https://github.com/aspnet/websdk/pull/174
I have reported the same behavior, and it turns out to be an issue only in the 64bit version of the MSBuild, switching back to the 32bit one worked for me, until this gets fixed.
Have a look at this link. It looks like the issue was previously fixed
https://github.com/Microsoft/msbuild/issues/1010
However, recently another change was made to MSBuild (referenced from above). My hunch is this 'downgrade' is causing the 'fix' to be ignored (wrong DLL ver is being used)
https://github.com/aspnet/Scaffolding/pull/321
I have projects in a solution going from Visual Studio 2010 to Visual Studio 2015 with Update 1. I just installed VS2015 with update 1 on a Windows 7 Continuous Integration build server and I'm getting the following errors. I've been digging around on the Internet for a couple days now with no leads on how to fix this. I've read similar posts on here that relate to other "packages" not being loaded but the recommended fixes haven't worked for this. I've uninstalled and reinstalled vs2015 a few times and still get the same errors. Any thoughts or ideas on how to fix?
Package 'VisualBasicPackage' failed to load.
C:\Workspaces\AHLTA\Current\Product\Production\Shared\Security\Security.vbproj : error : The application for the project is not installed.
Package 'VisualBasicPackage' failed to load.
C:\Workspaces\AHLTA\Current\Product\Production\Shared\Shared\Shared.vbproj : error : Project 'Shared' could not be opened because the Visual Basic 2015 compiler could not be created. Please re-install Visual Studio.
Package 'CSharpPackage' failed to load.
C:\Workspaces\AHLTA\Current\Product\production\DataLayer\Dmdc\Immunizations.Messaging\Immunizations.Messaging.csproj : error : Project 'Immunizations.Messaging' could not be opened because the Visual C# 2015 compiler could not be created. Please re-install Visual Studio.
UPDATE #1: I think I may have resolved this myself just now.
I found this post and tried the suggestion, now the build seems to be compiling correctly with no errors.
vs2012 error: package 'visual c++ package' failed to load
The information on the following link seems to have solved the problem I'm having. http://happyivyli.blogspot.com/2013/07/visual-c-package-failed-to-load.html
I recently migrated my VSTO Add in projects from "VS2008 and office 2007" to "VS2013 and office 2013", Changes took place as below settings.
.Net Framework version from 3.5 to 4.5(While upgrading project).
I have added VSTO 2013 PIA assemblies to reference.
That's it, when i tried to compile i have faced below MSBuild errors.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\OfficeTools\Microsoft.VisualStudio.Tools.Office.targets(268,13): error MSB4064: The "TargetFrameworkVersion" parameter is not supported by the "SignFile" task. Verify the parameter exists on the task, and it is a settable public instance property.
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v12.0\OfficeTools\Microsoft.VisualStudio.Tools.Office.targets(264,9): error MSB4063: The "SignFile" task could not be initialized with its input parameters.
and i have tried to find solutions over the internet but couldn't find much, Any Solutions for this problem will be helpful.
The problem was not the MSBuild, **
i have updated visual studio update 3 to update 4
and started working like charm.
I think Microsoft guys have moved something around from Update 3 to update 4 but this has been reported several times in many forums and i don't know why they have not mentioned it but this is one effective solution.
I ran into this issue. The problem is that Update 3 of Visual Studio 2013 moved some things around, so you need to use the MSBuild that is now installed with Visual Studio 2013 (or the standalone build tools for build servers). You need to make sure that you're using the correct MSBuild (currently at C:\Program Files (x86)\MSBuild\12.0\Bin), and it should work.
http://datatoknowledge.com/2015/01/30/vsto-and-visual-studio-2013-update-3/
Erick
This is still not working as of Visual Studio 2015 Update 3.
I had to actually modify the C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v14.0\OfficeTools\Microsoft.VisualStudio.Tools.Office.targets file and remove the TargetFrameworkVersion attribute from the SignFile task.