<![CDATA[AlternativeTo Dev Blog]]>https://dev-blog.alternativeto.net/https://dev-blog.alternativeto.net/favicon.pngAlternativeTo Dev Bloghttps://dev-blog.alternativeto.net/Ghost 1.7Wed, 08 Apr 2026 00:14:13 GMT60<![CDATA[You get the "CREATE MASTER KEY" error when importing a bacpac file from an Azure SQL DB]]>

I have ran into this issue twice now and have had to Google for it everytime. I thought i might as well post a little note here so i can remember it until next time. The solution to the problem is explained in this blogpost.

You have a few options

]]>https://dev-blog.alternativeto.net/you-get-the-create-master-key-error-when-importing-a-bacpac-file-from-an-azure-sql-db/5a3a18e125abf9217854cf0dWed, 20 Dec 2017 08:09:43 GMT

I have ran into this issue twice now and have had to Google for it everytime. I thought i might as well post a little note here so i can remember it until next time. The solution to the problem is explained in this blogpost.

You have a few options but i have used the Powershell script you can find here and then just run it like this.

C:\PS> .\RemoveMasterKey.ps1 -bacpacPath "C:\BacPacs\Test.bacpac"

Well, that's it :)

]]><![CDATA[Unable to Start Debugging on the Web Server after switch to https]]>

This post is mostly a Note to self™ post for future reference.

Just had a classic "Unable to Start Debugging on the Web Server" error thrown in Visual Studio. This error can have like 50 different causes and it's always hard to figure out why it happend.

As

]]>https://dev-blog.alternativeto.net/unable-to-start-debugging-on-the-web-server/59b0efa3327bceaf70d7baa2Thu, 07 Sep 2017 07:15:42 GMT

This post is mostly a Note to self™ post for future reference.

Just had a classic "Unable to Start Debugging on the Web Server" error thrown in Visual Studio. This error can have like 50 different causes and it's always hard to figure out why it happend.

As usual you get an answer or at least a push in the right direction on Stack Overflow. It turns out that my recently added "global redirect from http to https" added via "UrlRewriter" module caused the error in this case.

The solution was simple and pretty obvious, i just changed my starting URL to https://my-dev-domain.com instead of http://my-dev-domain.com. As i said, pretty obvious but still a confusing error message.

]]><![CDATA[Make your self-signed certificate trusted by Chrome]]>

When you are getting tired of that warning you get for your self-signed certificates when running your site locally you should add your certificates to your trusted certification store.

These instructions are for Windows and works for me™ in Chrome 60.

Create a self-signed certificate with a DnsName

Create a

]]>https://dev-blog.alternativeto.net/make-your-self-signed-certificate-trusted-by-chrome/59a56425c9d53c6544af6a3dTue, 29 Aug 2017 12:59:32 GMTMake your self-signed certificate trusted by Chrome

When you are getting tired of that warning you get for your self-signed certificates when running your site locally you should add your certificates to your trusted certification store.

These instructions are for Windows and works for me™ in Chrome 60.

Create a self-signed certificate with a DnsName

Create a new certificate with powershell "New-SelfSignedCertificate -DnsName localhost -CertStoreLocation cert:\LocalMachine\My". The DnsName is important and if you use a custom domain via a host file you should add the domain you use there.

Make sure you use this certificate on your localhost

Make your self-signed certificate trusted by Chrome

Export the certificate from Chrome

  1. Go to your localhost website and open up the inspector
  2. Under the security tab, click the "View Certificate" button.
  3. Go to the details tab in the dialog and click "Copy to file"
  4. Follow the wizard and choose the Cryptographic Message Syntax Standard - PKCS #7 (i do not think the "Include all checkbox" is important)
  5. Save it somewhere.

Import the certificate to the "Trusted Root Certification Authorites"

  1. Go to Chrome Settings
  2. Click advanced at the bottom
  3. Click the Manage Certificates link to open the certificate dialog
  4. Click import
  5. Follow the wizard and pick your exorted certificate file
  6. Click browse and choose "Trusted Root Certification Authorites"
  7. Done!

After this you should restart Chrome and you should not get any warnings.

All this information was collected at various places in this Stack Overflow question: https://stackoverflow.com/questions/7580508/getting-chrome-to-accept-self-signed-localhost-certificate

]]>