I am building a Visual Studio extension which also uses MonoDevelop.Xml. I found that when the MonoDevelop.MSBuildEditor extension is enabled together with my extension, both extensions stop working. The culprit is that both extensions declare the MonoDevelop.Xml.Editor assembly as a MEF component and that causes a conflict. If I remove the MEF component registration from my extension, both extensions work together, but then my extension does not work standalone.
I have no idea whether this could be fixed on my end, or both extensions and/or the underlying library need to be fixed. Any guidance?
Yet another problem is that the MonoDevelop.Xml library is not backwards compatible. The MonoDevelop.MSBuildEditor extension fails with a MissingMethodException when I use the latest version of the library in my extension. I worked around that by changing the strong name key of my library copy, so both can be loaded at the same time.
I am building a Visual Studio extension which also uses
MonoDevelop.Xml. I found that when theMonoDevelop.MSBuildEditorextension is enabled together with my extension, both extensions stop working. The culprit is that both extensions declare theMonoDevelop.Xml.Editorassembly as a MEF component and that causes a conflict. If I remove the MEF component registration from my extension, both extensions work together, but then my extension does not work standalone.I have no idea whether this could be fixed on my end, or both extensions and/or the underlying library need to be fixed. Any guidance?
Yet another problem is that the
MonoDevelop.Xmllibrary is not backwards compatible. TheMonoDevelop.MSBuildEditorextension fails with aMissingMethodExceptionwhen I use the latest version of the library in my extension. I worked around that by changing the strong name key of my library copy, so both can be loaded at the same time.