From time to time I would get into problems with persisted workflows, e.g. I could not resume it nor terminate it due to the system being unable to de-serialize workflows. If we change a workflow or any type that is serialized with it – there could be, actually there will be problems with long running and persisted workflows for sure.
WF 4.0 is much easier in this respect, since the new persistence provider serializes only the activities containing active bookmarks and the objects in the current scope. In many cases versioning effort can be limited by focusing on the fields added to the custom types, where .NET serialization attributes, such as [System.Runtime.Serialization.OptionalField] can be of great help.
I'm sure that over time you've run into the dreaded "File transport does not have read/write privileges for receive location "C:\Flatfile\SAPTestIn\".".
Usually you simply go to the folder and either give the BizTalk account full permission (bad) or Everyone full permission (really bad).
So for a production environment, what is the absolute minimum permissions required?
For the Receive File Adapter the explicit permission are:
| NTFS Attribute | Property Name |
| DELETE | Delete Files |
| FILE_READ_DATA | List Folder / Read Data |
| FILE_WRITE_DATA | Create Files / Write Data |
| FILE_APPEND_DATA | Create Folders / Append Data |
| FILE_READ_EA | Read Extended Attributes |
| FILE_WRITE_EA | Write Extended Attributes |
| FILE_DELETE_CHILD | Delete Subfolders and Files |
| FILE_READ_ATTRIBUTES | Read Permissions |
| FILE_WRITE_ATTRIBUTES | Write Attributes |
How does this translate into what to do in the System?
Right clicking on the folder and in the security tab,
setting "Modify" is not enough, though you would think so:
Strangely enough the Delete Subfolders and Files attribute is not set when the Modify property is set, you need to add the
FILE_DELETE_CHILD "Delete Subfolders and Files" Attribute:
Once you have added the Delete Subfolders and Files check box you will have the minimum permissions for the file receive adapter:
For the Send Adapter
The permission for the File Send adapter depends on what properties you have set in the Adapter Advance properties:
If you have the "Use temporary file while writing" flag un-checked then all you need are:
| NTFS Attribute | Property Name |
| FILE_WRITE_DATA | Create Files / Write Data |
If you have the "Use temporary file while writing" flag checked then the flags you need are:
| NTFS Attribute | Property Name |
| DELETE | Delete Files |
| FILE_WRITE_DATA | Create Files / Write Data |
| FILE_DELETE_CHILD | Delete Subfolders and Files |
| FILE_READ_ATTRIBUTES | Read Permissions |
This post gives needed details about the yet-to-go-public Panorama and Pivot controls. These can be found in the interim bits for those with special pre-launch agreements.
Jeff Wilcox – Looking ahead: Panorama and Pivot controls for Windows Phone developers
If you’re working with Azure, you really should be checking out AppFabric labs to get early exposure to new features. There’s a new preview for potential new features in the Azure AppFabric Access Control Service (ACS), including new support for Google, Yahoo, and Facebook identity providers. I have a blog post coming, but for more info see Justin Smith’s posting.
Easily get started creating Windows Phone 7 applications using the Caliburn.Micro framework and this Visual Studio project template.
More details at:
Visual Studio Project Template for Caliburn.Micro WP7 | SHAZAML!
Continuous integration is a concept that most in the industry are familiar with, but what about continuous delivery? Continuous integration, if you’re not aware, is the process of automating the building of your software project such that every time a change set is committed to the project’s version control repository, a dedicated build server will automatically build the software to ensure that there are no errors in the checked-in source code. Continuous delivery is an extension of continuous integration. During continuous delivery, the source code is built, but the end result is a packaged software project that can be released to QA (and possibly end users) with every check-in. More...
Windows Phone 7 UI Pattern for Pivot Views:
WP7 UI Pattern: Pivot Views | SHAZAML!
Post that describes the a Windows Phone 7 pattern for layered panoramas:
WP7 UI Pattern: Layered Panorama | SHAZAML!