<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ninject on InternetException</title><link>https://internetexception.com/tags/ninject/</link><description>Recent content in Ninject on InternetException</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 23 Feb 2020 13:54:58 +0100</lastBuildDate><atom:link href="https://internetexception.com/tags/ninject/index.xml" rel="self" type="application/rss+xml"/><item><title>Ninject and WCF</title><link>https://internetexception.com/2013/05/26/ninject-and-wcf/</link><pubDate>Sun, 26 May 2013 12:01:00 +0200</pubDate><guid>https://internetexception.com/2013/05/26/ninject-and-wcf/</guid><description>&lt;p&gt;Ninject is very simple and in the same time powerful IoC container. I used it in few project and had very little or none problems. Most of the time getting instances from Ninject kernel requires simple line with binding expression, or even this is sometime unnecessary if type is self bind able (i.e. if it is concrete class with parameterless constructor). Little harder is getting Ninject to work with WCF. You cannot just bind interfaces types because proxies which implements them are created through .NET mechanism. Luckily WCF system is very flexible and mostly can be changed/extended with custom functionality.&lt;/p&gt;</description></item><item><title>Ninject and Entity Framework</title><link>https://internetexception.com/2013/05/03/ninject-and-entity-framework/</link><pubDate>Fri, 03 May 2013 03:50:00 +0200</pubDate><guid>https://internetexception.com/2013/05/03/ninject-and-entity-framework/</guid><description>&lt;p&gt;&lt;a href="https://internetexception.com/2013/04/23/entity-framework-patterns-extension-and-unit-test-in-visual-studio-2012/" target="_blank" rel="noopener noreferrer"&gt;Last time&lt;/a&gt; I wrote about problem with testing Entity Framework in Visual Studio 2012. During working on this project I also encounter problems with configuration of Ninject to allow injecting Entity Framework classes from its Patterns extension. To be frankly this was not much a problem then lack of documentation. I just was forced to experiment with Ninject and new-thing-for-me Entity Framework Patterns extension.&lt;/p&gt;</description></item><item><title>Entity Framework Patterns extension and Unit Test in Visual Studio 2012</title><link>https://internetexception.com/2013/04/23/entity-framework-patterns-extension-and-unit-test-in-visual-studio-2012/</link><pubDate>Tue, 23 Apr 2013 02:18:00 +0200</pubDate><guid>https://internetexception.com/2013/04/23/entity-framework-patterns-extension-and-unit-test-in-visual-studio-2012/</guid><description>&lt;p&gt;Yesterday I was trying to make work simple test class in VS2012. I did not know what was wrong exactly. It was first project when I tried to glue together Entity Framework with repository pattern and Ninject as IoC container. Because of the fact that this was first time for solution like that I was sure that it is me, or rather source of my problem was indeed my code. But let&amp;rsquo;s not skip ahead.&lt;/p&gt;</description></item></channel></rss>