StuffOn.NET

In August 2014 Microsoft decided to remove Microsoft Azure Active Directory Access Control (also known as Access Control Service or ACS) from the default Azure Portal setup when creating a new Service Bus Namespace.   Shared Access Signature (SAS) is now default. Service Bus authentication through ACS is managed through a companion “-sb” ACS namespace and to create this we now need to do it from the Azure Power Shell command line (thanks Microsoft!) To do this: Download the PowerShell console https://azure.microsoft.com/en-gb/documentation/articles/powershell-install-configure/#Install Open up the Console and type Add-AzureAccount  and then type in the email address and password associated with your account (Work or Microsoft) Once authenticated you need to create the Service Bus Namespace so it's good to go for ACS. To do this you use the  New-AzureSBNamespace command Parameter Set: Default New-AzureSBNamespace [-Name] <String> [[-Location] <String&g

Whilst developing an Android App using Xamarin 5.1 I had issues deploying to the device. The exception was: Deployment failed because of an internal error: Unexpected install output: pkg: /data/local/tmp/com.mycompany.myapp.apk Failure [INSTALL_PARSE_FAILED_MANIFEST_MALFORMED] It turns out that this is down to the fully qualified naming of an activity. One of the changes with 5.1 is that you now need to fully qualify the Android Callable Wrapper Naming. So for example if you previously had: namespace MyNameSpace { [ Activity ] public partial class ActivityType : Activity { /* ... */ } } Then to maintain compatibility with your scripts/external code, set the  ActivityAttribute.Name  property: namespace MyNameSpace { [ Activity ( Name = " mynamespace .ActivityType" )] public partial class ActivityType : Activity { /* ... */ } } The important thing to note is is the case sensitivity of the Name decla