Mike Wills Podcast 2017-08-07 – Dog Days of Podcasting 2017-07

Here the next installment of the Dog Days of Podcasting podcast.

I talk about moving over to WordPress and my recording workflow a bit. Although it worked, I had issues with the URL that Auphonic got from Amazon S3.

Mike Wills Podcast 2017-08-06 – Dog Days of Podcasting 2017-06

Here the next installment of the Dog Days of Podcasting podcast.

I talk about our D&D adventure that we had last night (into the morning).

Mike Wills Podcast 2017-08-05 – Dog Days of Podcasting 2017-05

Here the next installment of the Dog Days of Podcasting podcast.

I talk about going to D&D that night and about the character that I play.

Mike Wills Podcast 2017-08-01 – Dog Days of Podcasting 2017-01

Here is my first installment of the Dog Days of Podcasting podcast. I dusted off the equipment and I took you on a journey to figure out what the hell this Dog Days of Podcasting will be about.

Forcing SSL in IIS without being annoying

When we recently launched our site, and with everything going to HTTPS only, I wanted to force as much to HTTPS only as possible. There are many, many links on how to force HTTPS on an IIS server. The issue is that when you debug your application locally, you have to comment out that section of code, do your debugging and changes, then hope you don’t forget to uncomment out that section of code. I have finally found out to the force HTTPS and allow you to debug on localhost. Here is the code that you need in your web.config:

<system.webServer>
  <rewrite>
    <rules>
      <rule name="HTTP to HTTPS redirect" stopProcessing="true">
        <match url="(.*)" />
        <conditions>
          <add input="{HTTPS}" pattern="off" ignoreCase="true" />
          <add input="{HTTP_HOST}" matchType="Pattern" pattern="^localhost(:\d+)?$" negate="true" />
          <add input="{HTTP_HOST}" matchType="Pattern" pattern="^127\.0\.0\.1(:\d+)?$" negate="true" />
        </conditions>
        <action type="Redirect" redirectType="Found" url="https://{HTTP_HOST}{REQUEST_URI}" />
      </rule>
    </rules>
  </rewrite>
</system.webServer>

The HTTP_HOST lines are what need to be added then it will work! Reference

Add Visual Studio Code to your context menu

After the release of the new Visual Studio Code, I took a look at it and figured out that the target market is those that are currently using Sublime Text. I want to give it the ol’ college try, but the one big thing that was missing for me is the ability to right-click on any file and open it in Visual Studio Code, like I can with Sublime Text.

Here is how to add this functionality. In the registry add the key HKEY_CLASSES_ROOT\*\shell\Open with Visual Studio Code\command with the value of @="C:\\Users\\USERNAME\\AppData\\Local\\Code\\app-0.1.0\\Code.exe \"%1\"" replacing USERNAME with your username. That is it!

A Fix for PDF Display Issues in Chrome

We came across an interesting bug in Chrome two days in a row, a PDF wouldn’t display correctly. It would be missing either an entire page or just some of the information on the page. There are published work-arounds to disable the built-in Chrome PDF viewer and instead utilize Adobe Acrobat Reader instead and also notices to maybe use a different browser. Let’s be honest here, the fault is the person/company that creates the PDF to make sure to optimze the PDF for the best viewing experience on the web.

Here is the problem, the Chrome PDF viewer cannot work with layered PDF files. I didn’t know layers was possible until just yesterday. Apparently, though I don’t yet know how, you can turn on and off layers (think of Google Maps with turning on and off features on the map). So how do you fix it? In both our our instances, we needed to flatten the PDF. Once we flattened the PDF and optimized it for the web, it showed up correctly in Chrome.

Don’t get me wrong, sometimes you will want those features and then you will need to provide a disclaimer stating that some PDFs may not render correctly in the Chrome browser. At least until Chrome adds support for layers.