-
Notifications
You must be signed in to change notification settings - Fork 86
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
Can't install the VSIX anymore #109
Comments
Same thing with VSIX built in VS 2012. |
Where do I get the VSIX? |
{SolutionDir}/CPPCheckPlugin/bin/Debug/CppcheckPlugin.vsix Isn't VSIX the only way to install the plugin into VS, short of running debug which creates a sandbox instance? I mean, how do you even use the plugin without running its VSIX? |
I cannot reproduce the problem. Do you have an idea of when it appeared for the first time? Maybe there's a specific commit such that it doesn't occur before that commit? |
It happened between the last time I committed and today, and the problem is not with the source code - I've reverted back to where it certainly worked, and still got the same error. It's something in my environment. I just thought you might know what could cause it. |
Not a slightest idea. |
Today I decide to install VSIX v1.2.1 and I have similar problem. I think it is not source code bug, but Visual Studio. I installed Visual Studio CTP5 two weeks ago and found some problems with my OS since then like hangs on creating System Restore Point. |
It's definitely not a source code bug or VSIX file bug. It's a bug in our local environment. |
Actually the problem comes from the fact that VS 2015 CTP / RC comes with .NET 4.6 RC and so .NET 4.5 is no more seen by VSIX.
|
Fix issue #109: allow .NET versions > 4.5.
When I run the VSIX on my main working computer, I get an error:
Install Error : Microsoft.VisualStudio.ExtensionManager.MissingTargetFrameworkException: The extension 'cppcheck add-in' requires a version of the .NET Framework that is not installed.
This is a VSIX built with VS 2013. At the same time, if I open the solution in VS 2013 and launch debug, debugging works fine.
Thoughts?
The text was updated successfully, but these errors were encountered: