Skip to content
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

Use dynamics to avoid binding to specific version interfaces. #12

Merged
merged 1 commit into from
Feb 6, 2014

Conversation

Dmitry-Me
Copy link
Collaborator

This pretty much gets rid of Microsoft.VisualStudio.VCProjectEngine static dependencies which resolves the following problem (reported here #10 (comment) )

I can't make the same package work for both VS2012 and 2013 (2010 is out of the question for now, there's a problem with manifest file for it). I've just built the project from repository (which is for VS2012) in 2013, and installed the package into both VS2012 and 2013. As soon as I save a file in 2013 I get a message: "Exception occurred in cppcheck add-in: Unable to cast object of type 'Microsoft.VisualStudio.Project.VisualC.VCProjectEngine.VCProjectShim' to type 'Microsoft.VisualStudio.VCProjectEngine.VCProject'."
This is beause the project is importing v11.0 assemblies, and VS2012 uses v12.0.

Dmitry-Me added a commit that referenced this pull request Feb 6, 2014
Use dynamics to avoid binding to specific version interfaces.
@Dmitry-Me Dmitry-Me merged commit f761be4 into VioletGiraffe:master Feb 6, 2014
@Dmitry-Me Dmitry-Me deleted the dynamicsforvcproject branch February 25, 2014 08:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant