Mike Taulty's Blog - All Comments

Social comments and analytics for this post

uberVU - social comments — Fri, 12 Mar 2010 04:42:51 GMT

This post was mentioned on Twitter by jrguay: Silverlight 4, MEF and the DeploymentCatalog ( again :-) ): The Silverlight 4 beta came with a versio... http://bit.ly/bVq6Qt (by @mtaulty)

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

Anonymous — Thu, 11 Mar 2010 06:16:27 GMT

It is OK! I can run it.

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

mtaulty — Thu, 11 Mar 2010 00:36:09 GMT

I updated the zip file again. Hopefully this time it's correct - apologies for the false starts, I hadn't realised there was so much in this zip file.

BTW - FloatableWindow is taken from CodePlex - generally useful class for Silverlight apps.

Mike.

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

Anonymous — Wed, 10 Mar 2010 18:19:57 GMT

I downloaded new code. It seems that in the solution the project is unavailable again. When I reload the project I am getting wrong path name. What I did I removed the project and added again “Add Existing Project”. I built the project thereafter. I am getting errors in MEFDemo project on CatalogBits (e.g. using CatalogBits.Loading;) I added mtaulty.deploymenttext as a reference to MEFDemo project. It is OK for now. It complains on FloatableWindow.dll. Should I download the dll from somewhere?

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

mtaulty — Wed, 10 Mar 2010 13:45:49 GMT

You are not wrong. I'm having a bad day for downloads! I've replaced the version of the ZIP file. Let's see if I can get this right at some point today :-)

Mike.

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

Anonymous — Wed, 10 Mar 2010 08:04:57 GMT

Cannot build the project, mtaulty.deploymentext project is unavailable

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

mtaulty — Wed, 10 Mar 2010 07:30:32 GMT

Apologies about the missing download - not sure what happened there but I have replaced it and it should be there now.

Mike/

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

Anonymous — Wed, 10 Mar 2010 07:11:13 GMT

Cannot download the file from mtaulty.com/.../SL4MEFNotepadEtc.zip

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

Glenn Block — Wed, 10 Mar 2010 07:09:28 GMT

Mike you are awesome. You might have just given my MIX talk another boost :-) Hope you don't mind me stealing this from you.

re: Silverlight 4, MEF and the DeploymentCatalog ( again :-) )

Tyler — Wed, 10 Mar 2010 02:33:30 GMT

I can't seem to download the code file. Any ideas? I'm getting a 404. I'll try later, but meantime can you check it out? Thanks, -Tyler

MEF and the DeploymentCatalog

Mike Taulty's Blog — Tue, 09 Mar 2010 23:31:29 GMT

The Silverlight 4 beta came with a version of MEF that had 3 catalogs – namely AssemblyCatalog, TypeCatalog

MEF and the DeploymentCatalog

Mike Taulty's Blog — Tue, 09 Mar 2010 23:31:28 GMT

The Silverlight 4 beta came with a version of MEF that had 3 catalogs – namely AssemblyCatalog, TypeCatalog

MEF and the DeploymentCatalog

Mike Taulty's Blog — Tue, 09 Mar 2010 23:31:27 GMT

The Silverlight 4 beta came with a version of MEF that had 3 catalogs – namely AssemblyCatalog, TypeCatalog

re: Website Rehosting – Mail Me If You Have Problems

mtaulty — Tue, 09 Mar 2010 16:03:29 GMT

Siegried,

Sorry - perhaps I've given you the impression that I am setting up a site for answering general questions. I'm not :-)

I really meant "Mail me if you have problems" with my newly re-hosted website.

On your specific issue - I'm afraid I've got no idea at this point as it must be almost 4 years since I've looked at WSE. The best I can offer is to look to the forums over here social.msdn.microsoft.com/.../threads to see if someone can help?

Mike

re: MEF, Silverlight and the DeploymentCatalog

mtaulty — Tue, 09 Mar 2010 16:00:42 GMT

Bill,

You made me go and re-watch my own video :-)

In the video we have a main application.The main application imports plugins and the plugins depend on a singleton service.

All the main application knows is that it imports plugins.

All the plugins know is that they import a singleton service.

The main application loads XAPs and adds those XAPs to a catalog. This could easily be factored out into an XML configuration to take this "knowledge" away from the main application. The application does not know which components live in which XAPs or even what components are actually in the XAP so it's really just "dumb loading" a set of XAPs and we could easily factor that out into some other component that was declaratively driven.

Hope that makes sense,

Mike