Embedding the types only makes the assembly bigger for no benefit.
And it does screw up debugging for anyone doing VS extensibility, where you start getting errors like this:
soln.Projects.OfType<EnvDTE.Project>()
Embedded interop type 'EnvDTE.Project' is defined in both 'EnvDTE.dll' and 'NuGet.VisualStudio.dll'. Some operations on objects of this type are not supported while debugging. Consider casting this object to type 'dynamic' when debugging or building with the 'Embed Interop Types' property set to false.
(here I was trying to inspect the current solution in a quick watch window)
See:
- http://blogs.msdn.com/b/samng/archive/2010/01/24/the-pain-of-deploying-primary-interop-assemblies.aspx
- http://mschnlnine.vo.llnwd.net/d1/pdc08/PPTX/TL16.pptx
- http://blogs.clariusconsulting.net/kzu/check-your-embed-interop-types-flag-when-doing-visual-studio-extensibility-work/
on why this COM-inspired feature should not be considered a general-purpose versioning story for nuget, since it breaks the typical developer flow for VSX authors.
Comments: Thanks, that would be awesome! It should be enlightening for anyone doing VSX work and shipping utilities/runtimes for use by other VSIXes...
And it does screw up debugging for anyone doing VS extensibility, where you start getting errors like this:
soln.Projects.OfType<EnvDTE.Project>()
Embedded interop type 'EnvDTE.Project' is defined in both 'EnvDTE.dll' and 'NuGet.VisualStudio.dll'. Some operations on objects of this type are not supported while debugging. Consider casting this object to type 'dynamic' when debugging or building with the 'Embed Interop Types' property set to false.
(here I was trying to inspect the current solution in a quick watch window)
See:
- http://blogs.msdn.com/b/samng/archive/2010/01/24/the-pain-of-deploying-primary-interop-assemblies.aspx
- http://mschnlnine.vo.llnwd.net/d1/pdc08/PPTX/TL16.pptx
- http://blogs.clariusconsulting.net/kzu/check-your-embed-interop-types-flag-when-doing-visual-studio-extensibility-work/
on why this COM-inspired feature should not be considered a general-purpose versioning story for nuget, since it breaks the typical developer flow for VSX authors.
Comments: Thanks, that would be awesome! It should be enlightening for anyone doing VSX work and shipping utilities/runtimes for use by other VSIXes...