Package Installation Error In Microsoft Visual Studio 2019 - installation

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.

Related

Xamarin Error, following tutorial, dependencies issues for days

Using Visual Studio 2017, Community Edition.
I'm doing the tutorial (/guides/xamarin-forms/getting-started/hello-xamarin-forms/quickstart/) for Xamarin and I'm getting a similar error, whenever I try to update any of the Android packages. If I try to update Xamarin.Androix.Support.Vector.Drawable, I get the following error message:
Severity Code Description Project File Line Suppression State
Error Unable to resolve dependencies. 'Xamarin.Android.Support.Vector.Drawable 25.4.0.2' is not compatible with 'Xamarin.Android.Support.v7.AppCompat 23.3.0 constraint: Xamarin.Android.Support.Vector.Drawable (= 23.3.0)'. 0
I went to the Android SDK manager and updated everything I could find there, still no luck. Any advice is much appreciated.
You need to first upgrade Xamarin.Android.Support.v7.AppCompat. If it's an option, you could just upgrade ALL packages in one shoot using update option from Packages context menu on the solution explorer.

msi installation failure (Error 1001. InstallUtilLib.dll: Unknown error. DEBUG: Error 2769: )

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.

How to fix VS2015 Package 'VisualBasicPackage' failed to load?

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

VS 2013 error: Could not load file or assembly 'Microsoft.PowerShell.Security' or one of its dependencies

I'm getting this error in Nuget Package Manager Console window, please see image attached. I think because of this I can not install an older version of package I need (Umbraco CMS) - during installation similar strange error arises with a bit different messages. I've checked this on different computer - without this error older package is being installed properly.
Tried re-installing Visual Studio 2 times - no effect. I could not achieved clean re-install, new VS instance inherits many plugins and features from previous instance.
Please somebody help me with this issue. Thanks in advance!

Visual Studio Extension: Build error VSSDK1043: "There was a prblem finding the extension with a VSIX identifier..."

I am trying to debug my extensions and suddenly I cannot build it anymore.
Error 1 There was a problem finding the extension with a VSIX
identifier of "1cdefdc6-1f5e-4027-9bb7-773248c65070". Illegal
characters in path.
I have rolled back all changes I made and still the error occurs. I don't think that I have changed any configuration.
This is not a dupliacte of: VSIX package build failed without showing the reason (Visual Studio bug) I have already tried those suggestions.
If I disabled
Deploy VSIX content to experimental instance for debugging
it compiles, but I cannot debug it.
Changing the Product ID also works, but this means, that it can no longer update the existing product.
I was getting the same error message (this is how i ended up hear) and then after changing the name i got the following error
VSIX development error VSSDK1040: There was a problem enabling the extension with a VSIX
Stumbled on the solution found here
What he did was delete this folder C:\Users\<UserName>\AppData\Local\Microsoft\VisualStudio
So i did that, am going to have to re-install a handful of extensions now as i am getting errors from them but it did correct my issue.
maybe you can dig a little deeper into the folder to find just the needed items to remove or do what i did and just nuke the folder and pick up the pieces
EDIT: from comments you may be able to get away with just removing anything under 'C:\Users\\AppData\Local\Microsoft\VisualStudio' with the EXP extension

Resources