If you work with SharePoint custom site templates regularly, and your organisation has separated development, test, and production environments, then you’ll probably have come across the issue where a custom site template you’ve saved in one environment as a solution package (WSP) uploads and activates fine in another environment but then fails with the familiar obscure message and correlation ID when you attempt to create a new site.
Everyone knows how to create lists via the web browser, but for developers it can often be easier and more controlled to use automation to create lists on target SharePoint sites, for custom solutions they are developing, and the easiest way to do that is often using PowerShell.
Loading (well, reloading) workflows that include Visual Basic expressions in a WCF hosted service is not as straightforward as one might expect. If you have created your XAML workflow based on an ActivityBuilder or a DynamicActivity then the Visual Basic settings aren’t configured automatically.
Generating an in-code representation of an XML schema is pretty straight-forward, using native classes in the .NET Framework. This article covers how to read the XML, and generate the appropriate class files to support that.