Recently I was tasked with the task of creating an automatic extraction and importing solution using PowerShell Scripts. To do this I created two files one for export and extracting with the other in charge of pack and importing the solution. I was using the Visual Studio template of CRM Package that comes with the sdk.
Export and Extracting The Solution
First thing I did was implement the export and extraction of the CRM solution. The PowerShell script first exports the solution from the web using a module called Microsoft.Xrm.Data.PowerShell. Then it extracts the downloaded zip into a folder for the correct file structure. A nice thing about using the Microsoft.Xrm.Data.PowerShell dll is the fact it gives you additional CRM commands you can do. For example before downloading the solution it allows you to change the version number of the solution before downloading.
Microsoft’s XSD utility provides an excellent way to generate classes from schema definition files, but has a few quirks that can make using the generated classes a bit tougher. In particular, it serializes repeating structures as arrays rather than using the generic List class, and it serializes any element with a “minOccurs = ‘0’” with a separate “Specified” property (which must be set to true if the member is to be serialzied back to XML).
We frequently use serialization techniques here, and while there are some utilities out there that offer similar post processing, many of them are not free and/or difficult to package with a build (include an executable in the project? not ideal). In light of that, I wrote a PowerShell script (below) that can be included in source control and utilized in a post-build event. For example,
The short version of this story is: Before uploading a VHD to Azure, make sure you’ve enabled remote RDP (installing Azure PowerShell is a good idea too). But if you forget (and your VM is running Windows Server 2012), it can be fixed without having to redo a massive upload.
We recently did a demo for a prospective client, and wanted to give that client access to the VM the demo was on to further explore and tinker with the solution. Azure IaaS makes perfect sense here – upload the VM right to Azure and let the client have access. The VM can be spun up on demand, and can be removed when it’s no longer needed – and it won’t require any special permissions or network/firewall rules on either end.
There are several helpful guides to prepping and uploading a VHD…
Recently we had a problem with an internal application that is hosted on Azure PaaS. Windows Authentication would be disabled periodically for our Cloud Service. This would cause our application to return a 403 error to all visitors because we required that users be authenticated before accessing the application. Originally we didn’t have this issue with our application on Azure, but at some point the default IIS configuration changed and we started seeing this issue when a new role was started.
Microsoft Azure BizTalk Services (MABS) has a lot to offer for companies looking for a PaaS Middleware solution. EAI bridges provide B2B communication as well as LoB access functionality for EDI, XML, and flat file interchanges. The new mapping system offers some exciting and powerful new functionality as well, vastly simplifying certain tasks that previously required several functiods, and opening up new possibilities and enhanced performance with lists.
However, it is a new technology, and certain tasks that have been very straightforward in BizTalk Server 2013 require a different way of thinking for MABS. For example, it is a fairly trivial task to create an orchestration that accesses a LoB adapter (using, for example, WCF slqBinding) to do data validation or enhancement, and publishing this orchestration as a web service for client consumption. If your SQL database is SQL Azure, there…
This post describes setting up PSRemoting to allow execution of PowerShell commands on your SharePoint 2010 Server instance from your FAST Search server instance. These instructions should work however between any two machines on the same domain.
Setting Up PSRemoting
First, PSRemoting needs to be enabled on both the FAST and SharePoint servers. Launch a PowerShell session as Administrator on each machine, and run the following command:
You will then be met with various prompts, asking you to approve execution of PowerShell commands to enable remoting. Answer Y for each and hit Enter.
Enabling CredSSP Authentication on the Client (FAST)
The authentication type we will be using is called CredSSP. This needs to be enabled as well on both the client and server machines.
On the FAST server (which will be our client), execute the following command:
Enable-WSManCredSSP –Role Client –DelegateComputer sharepointcomputer.mydomain.local
You will see the following…