Posted By: Jason Olson | Jul 13th @ 11:24 AM | 56,330 Views | 10 Comments

In this episode of 10-4, we take a look at a new library in .NET Framework 4 and how it helps developers write applications that are more extensible and easier to maintain than before.

For more information on the Managed Extensibility Framework, make sure to check out its home on Codeplex: http://www.codeplex.com/mef.

Source code for demo: http://cid-1b51ad25aad8fc86.skydrive.live.com/self.aspx/.Public/ManagedExtensibilityFramework.zip

For more 10-4 episodes, be sure to visit:
http://channel9.msdn.com/shows/10-4

10-4! Over and out!

Rating:
3
0
JoshRoss
JoshRoss
A righteous infliction of retribution manifested by an appropriate agent.

Nice intro!  I had a question, and I tried looking around the CodePlex documentation first, and did not find the answer.  

This is more of a problem with my documentation reading skills than the authors document writing ability.

Anyways, back to the question, if I have two or more equivalent exports, that have their imports satisfied, how is the import resolved? First in wins?  I think it has something to do with the catalog.

Remco Ros
Remco Ros
.Net developer

Very nice, especially the part about the NetworkCatalog.

So you mention that the source is (will be?) available online. But I cannot find a link or attachment?

 

Remco.

JoshRoss
JoshRoss
A righteous infliction of retribution manifested by an appropriate agent.

It was in the post comments... http://www.codeplex.com/mef

Remco Ros
Remco Ros
.Net developer

That's the MEF site. I mean the source from this presentation/example application. (or is this included in MEF Samples?)

[Obsolete]

System.AddIn

 

Very good explanation of MEF. I was looking into Spring.Net. How is MEF compared to Spring. Is it configurable using XML files or is it done through code.

 

Why not Spring.Net?

 

Just want to hear your take on it; I'm new to Dependency Injection.

 

Thanks.

Omg, this is very cool.. great episode..

 

I was wondering if there are any performance implication when linking dependencies to all objects?

Also, if you can talk more on further episodes about what other features like this will come in .net framework 4 that help us follow other best practices, patterns or SOLID principles easily.

 

Again, great job!

 

Thanks,

Microsoft Communities