Writing some async unittests in combination with structuremap gave me an ugly exception
System.MissingMethodException: Method not found: ‘Void StructureMap.AutoMocking.AutoMocker`1..ctor(StructureMap.AutoMocking.ServiceLocator)’.
Result StackTrace:
at StructureMap.AutoMocking.RhinoAutoMocker`1..ctor(MockMode mockMode)
After reading about the Structuremap 3.1 update the exceptions were gone. Updating the nuget to 3.1 solved it.
update-package structuremap
Last week recap and links:
Image courtesy of kanate / FreeDigitalPhotos.net
What are your best reads this week? Leave them in the comments below.
On twitter I read this post:
I decided to go for the Run.Blog.Hop. event. Virtual Running UK organizes races you can enter by sending your stats and a screenshot from your running app.
This reminds me of the Automattic’s Worldwide WP 5k. When will that be organized again?
Here’s me finishing the venloop in 2014. Keep running!
Visual Studio notified me that using WCF is not permitted in the starter edition of Xamarin. I needed to login and buy the Business Edition.
Then I found the beginning a xamarin trail in the developers guides. Just login or create a xamarin user and start the trail right from the popup.
Last tip: Xamarin has Exclusive offers and pricing for MSDN subscribers
Microsoft offers a tool to manipulate the installation of MSI.
Orca let’s you create a transform file to change almost everything. You can also view the properties the MSI uses internal to control the installation steps. Both can be applied to the MSI from the commandline. Together with the Quite install this can make your installations a little easier.
You can create a transform (MST) file with Orca. First load the MSI, then start a new Transform (Transform > New Transform). Every change you make is logged. When done you can save the changes to a file. (Generate Transform)
Call the MSI from the commandline
msiexec /qn /i your.msi TRANSFORMS=your.mst
Another way to influence the installation is with properties. Orca shows the properties in the Property table. (see screenshot) You can change the value used during installation by specifying the value on the commandline.
msiexec /qn /i your.msi INSTALLATIONTYPE="Server"
I’m using this to configure and install test machines in Azure. From powershell you can create an AzureVm, start a session to the new Vm and install the MSI the way you need it.
.NET Development by Eric 