Via Paul, this new paper on MSDN lays out some interesting tests to provide developers with information about some of the design impacts when using WF. These are always fun to read and then later to watch people hold them up as gospel about why they made really weird design choices. 🙂 Please, take these for what they are: guidelines and information. Don’t decide that you’ll never use a while activity because it is slower than some other activities. Test on your own system and add some complexity with custom activities if you really need the performance.
Search this Site:
Recent Posts
- Logic App Consumption deployment: The secret of KeyVault parameter cannot be retrieved. Http status code: ‘Forbidden’. Error message: ‘Access denied to first party service
- BizTalk Server Visual Studio project: attempted re-targeting of the project has been canceled.
- BizTalk Oracle Adapter error: The assembly required for type mapping not found.
- PowerShell script to identify all SQL V1 actions and triggers inside Logic Apps Consumption
- Friday (funny) Fact: There is no size limit for the Logic App parameter name