<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Dependency Injection on VacuumBreather</title>
    <link>https://www.vacuumbreather.de/tags/dependency-injection/</link>
    <description>Recent content in Dependency Injection on VacuumBreather</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Mon, 13 Apr 2020 00:00:00 +0000</lastBuildDate>
    
	<atom:link href="https://www.vacuumbreather.de/tags/dependency-injection/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Debugging MEF</title>
      <link>https://www.vacuumbreather.de/blog/mef_debugging/</link>
      <pubDate>Mon, 13 Apr 2020 00:00:00 +0000</pubDate>
      
      <guid>https://www.vacuumbreather.de/blog/mef_debugging/</guid>
      <description>If you have ever worked with a Dependency Injection container like MEF, you have probably run into the problem of types not being resolved correctly. Since MEF works mainly by attributes, typically the Export attribute on the class declaration, all it takes is a missing attribute for some type to go missing during bootstrapping.
This can also be the case in a test application, when most of the classes of one layer have been mocked away, and there is always that one mock that cannot be found.</description>
    </item>
    
  </channel>
</rss>