Maarten Balliauw {blog}

Hi Maarten

Thanks for sharing the demo code. It's all very exciting technologies.
I have found a little glitch in the msbuild script(might not be a glitch at all depending where you put the source code):

<Exec WorkingDirectory="$(PackagesPublishDir)"
          Command="$(NuGetExe) pack $(BuildDir)\temp\Package\package.nuspec" />

Above line gives a msb error with exits code of 9009. After I added escaped quots around the command and params, it works:
<Exec WorkingDirectory="$(PackagesPublishDir)"
          Command="&quot;$(NuGetExe)&quot; pack &quot;$(BuildDir)\temp\Package\package.nuspec&quot;" />

But I still have to run the build script for a number of times to get rid of an "assembly or dependencies not found error" in all the build scripts of the components at line 40. Seems you have to run it twice to build each of them. I can't figure out why.

Food for thought here Maarten. I know what you have demoed is probably what a lot of people are after. But what if there's a SOA element? For example: you have a dependency of a wcf server in your controller, how would you go about using MEF to inject the dependency? I tried manually adding mef export attribute to the service client, it worked but not ideal. I changed the wcf service so that it lends iteslf to MEF. But the generated client proxy hasn't got any MEF attributes at all. I don't know how feasible is it to extend svcutil.exe to do that leg work. Is there any way to do this automatically?
Thanks.

Hi Maarten

Thanks for the suggestions. Option 1 and 4 sounds interesting. I will give them a go. Also that's a good tip about config transfer using NuGet.

Thank you very much

Talks

Talks