WF and WCF integration in .NET 3.5

I think the commentary is be smarter about how you distribute dlls. If 2.0 folder exists. Use the DLLs you can there and just add 3.0 dlls ADDITIVE DLLs.
The unabashed truth and maybe you can comment on this more:
Microsoft takes the least resistant path to distribution. Not the smartest.
If Microsoft wanted to it could logically figure out which DLLs are needed and install those.
The answer you are shying away from, Matt is Microsoft is not committed to optimizing the framework install process.
The 1.0 and 1.1 directories are there for compatability reasons. If you compile an application for 1.1 and you have 3.0 installed, it will run on the CLR used by the .NET Framework 3.0.
If you install the .NET Framework 1.1 on that machine, that same application will run on the .NET Framework 1.1.
The folder structure (and the config files in them) are part of the mechanism that provides that CLR affinity. This was and is a feature set important to our user community and partner ecosystem.
I do think we are commited to optimizing the .NET Framework install process, and I don't think one can measure that by a single metric like footprint. We have other products (Silverlight 1.0 and 1.1) that have a much smaller footprint.
--Justin Smith
http://blogs.msdn.com/justinjsmith
hello Guys,
do you think we have the view capacity of superman? the video qulaity sucks and is impossible to read any single line of code.
Please next time use different type of recording otherwise the video is worthless and would be better to post a podcast.
Luigi