Today's featured TechNet Wiki article can be found here. It was originally authored by Mike McKeown.
Q: What do I need to do to my WF or WCF applications to have then work in AppFabric? A: There are no special requirements for creating an application beyond ensuring that the application can be hosted in the WAS hosting environment. The default project templates in Visual Studio guide you to build a service that will run in AppFabric. If you have applications that are hosted in WAS currently, they can be deployed to AppFabric without any requirement to modify the project source.
Q. If I have Workflow A and Workflow B, if I then have a new version of each, do I end up exposing 4 workflows? A: As far as AppFabric is concerned each of these are separate workflow services. There is no explicit versioning support in AppFabric. You will have to implement it using .NET support for versioning.
Q: Are you planning to get rid of the existing WCF client test client and host? A: No, the test client will work with the WCF services running on AppFabric.
Q: What .NET version of my WF or WCF service will run with AppFabric? A: AppFabric primarily supports the .NET Framework version 4. Therefore any WCF or WF service written with an earlier version of the .NET Framework Libraries will not be able to take full advantage of the AppFabric features.
Q: When I build my services I want to minimize the number of configuration settings the admin can modify. So most of my WCF settings are hard coded. Since IIS has complex configuration model how can I hide this complexity from my users? A: IIS 7 support configuration locking. While it doesn’t hide the configuration it provides a way to prevent the local admins from overriding the configurations defined globally.
Read the rest here, including a section on AppFabric Caching!
This article is also available in the following languages: