-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package not loaded anymore in VS2017 V15.4.0 #84
Comments
It seems like this is an issue with your VS installation. Please try the steps described on this site:
if this does not work, maybe try the steps described on this site. |
A coworker and I are both having the same issue. The solutions above did not fix it. It is happening to me in VS 15.4.0 and 15.4.1. ActivityLog info is the same as previously reported. I did have Visual Studio 2015 installed as well (where License Header Manager was working fine). In my attempts to resolve this error, I have uninstalled VS 2015 and performed a repair on the VS 2017 installation, but it didn't help. |
You could try deleting/renaming the ComponentModelCache Folder It should be located under |
I've done that several times. Last time was just 5 mins ago. No luck. |
I think i found the error location. Please uninstall your current LicenseHeaderManager version and try the version below: |
That works! Thanks so much! |
Nice! Sry for the inconvenience! |
It works! Thanks for your support! |
Nice! We will include the fix in the next official release :) |
VS Acitivity Log is:
233
2017/10/13 07:41:06.541
Information
80020006
235
2017/10/13 07:41:06.563
Error
SetSite failed for package LicenseHeaderManager.LicenseHeadersPackage, LicenseHeaderManager, Version=2.0.2.0, Culture=neutral, PublicKeyToken=cdd89d39b9f20fb0
{4C570677-8476-4D33-BD0C-DA36C89287C8}
80020006
236
2017/10/13 07:41:06.567
Error
End package load [LicenseHeaderManager.LicenseHeadersPackage, LicenseHeaderManager, Version=2.0.2.0, Culture=neutral, PublicKeyToken=cdd89d39b9f20fb0]
{4C570677-8476-4D33-BD0C-DA36C89287C8}
80020006
The text was updated successfully, but these errors were encountered: