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
Related
Please I was busy for the past 4 days trying to fix the issues resulting from the below error. Please how do I go about fixing this error below?
*Severity Code Description Project File Line Suppression State
Error: Failed to add reference to 'comerr64'.
Please make sure that the file is accessible, and that it is a valid assembly or COM component.
*
So I tried reinstalling the Microsoft visual studio 2019 to see if things would go well but all trials were to avail. Then I've also tried several times to reinstall the Nuget package "MySql.Data (8.0.32) by oracle, 54.1M downloads" after all trials to fix this but all I got was same error.
There is bug with MySqlData 8.0.32. The workaround is installing MySqlConnector. This link explains it:
https://mysqlconnector.net/troubleshooting/failed-add-reference-comerr/
The error message went away once it was installed and the site is working.
I left MySqlData in the manifest (installed) for now because there are some dependencies to the other MySQL assemblies that require MySqlData installed that will make if difficult to remove at this point.
What to do to solve "The “GetDeploymentPathFromVsixManifest” task failed unexpectedly" when trying to debug a VS extension project??
Same question was already asked multiple times with different source reasons, all for VS2017 usually for upgrading VS extensions from VS2015, and it should have been solved with VS 2019. Yet, it just popped up.
The "GetDeploymentPathFromVsixManifest" task failed unexpectedly.
System.TypeLoadException: Method 'get_JoinableTaskFactory' in type 'Microsoft.VisualStudio.Sdk.BuildTasks.ExtensionEngineHost' from assembly 'Microsoft.VisualStudio.Sdk.BuildTasks.16.0, Version=16.9.2017.12405, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' does not have an implementation.
at Microsoft.VisualStudio.Sdk.BuildTasks.ExtensionManagerUtilities.GetExtensionEngine(ISettingsManager manager, Boolean deletePendingUninstalls)
at Microsoft.VisualStudio.Sdk.BuildTasks.GetDeploymentPathFromVsixManifest.Execute()
at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__26.MoveNext()
I have tried all the solution for the same error found on SO, so far to no avail. I am using VS 2019 Community 16.9.2, updated all packages, downgraded some to try, nothing really changes this error.
This is my first attempt on VSIX and I just downloaded an existing project from github and compiled it.
The github project is working (probably) since the extension is available on the marketplace.
Any other suggestions? Searches on this error in combination with the JoinableTaskFactory dont return exactly many results.
For me the solution was to do at least one of the following steps:
Delete the obj-folder in the project
Execute Reset the Visual Studio 2019 Experimental Instance. You can find this tool when you search it in the windows search bar.
Clean and Rebuild the project
Sometimes it helped if I did only one step and sometimes it only worked after doing all the steps.
I couldn't find out if there is a specific pattern behind, but doing all of the above steps always fixed the error for me.
Another issue where I got the same error was if there was the wrong external program selected under Project Properties -> Debug -> Start external Program. For VS2019 I need to select C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\Common7\IDE\devenv.exe
If I switched between Visual Studio Versions, then sometimes a different Visual Studio version was selected.
Uncheck: "Deploy VSIX content to experimental instance for debugging"
in solution properties->VSIX
Also Update installed NuGet packages.
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!
Eariler, We had our solution built with visual studio 2010 and we had .vdproj file for creating the build and it was working fine perfectly.(setup is installed and works as expected).
But recently, we have upgraded our solution to visual 2017. We did the migration successfully but for build or setup .vdproj was not working fine as we were not able to open .vdproj in visual studio 2017. So, I just googled around & found out the following solutions:
Install visual studio installer plugin in 2017
User InstalledShield Limited editions
We have gone with first option. We just installed that plugin. Post this, We are able to open that existed visual studio 2010 .vdproj in visual studio 2017. It got migrated without any error. We had custom actions(primary output) in the project, we just re-added them. *.vdproject gets complied successfully and generates .msi file
But while installing it by command line or explicit(double click the .msi). We get following error:
Error 1001. Error 1001. InstallUtilLib.dll: Unknown error.
DEBUG: Error 2769: Custom Action _71938623_DFF8_4B88_8552_77D8706A0C48.install did not close 1 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769.
The arguments are: _71938623_DFF8_4B88_8552_77D8706A0C48.install, 1,
CustomAction _71938623_DFF8_4B88_8552_77D8706A0C48.install returned actual error code 1603
(note this may not be 100% accurate if translation happened inside sandbox)
After googling a bit about this, We found couple of suggestion such as adding or removing slash in arguments using command line installation.
But even though we are doing explicit installation(by double clicking the setup file) still we get the above mentioned error.
In case, We remove the custom action from project installation, then msi gets installed successfully. So, we don't know what is the problem with those custom actions.
We tried of debugging custom action by using Debugger.Launch(). But installer doesn't reach that portion. Prior to that we get above mentioned exception.
Don't know what to do.
We are scratching our head. Any suggestion or help would be really appreciated.
Could it be because of .net framework installed. we have installed .NET 4.6.1 too.
I am trying to Build list of Projects, which was developed on MVC3 using visual studio 2012 with .net framework 4.
When I try to Build solution using VS2017, I am getting nuget Package error on restoring it.
I went all the possible solutions-
Tried to uninstall and reinstall it.
Changed framework and cleaned the solution.
But, still I cannot get rid of the error. Can anyone help me ?
This is the error which I am encountered with
When I try to reinstall or update or restore it.I am getting following error
It is pretty simple actually and a common oversight.
If you check,you will find out the visual studio 2017 does not support mvc3.
Update accordingly