In my environment, I always build and test websites using SSL, so I don't run into any surprises when we push code to production where SSL is almost certainly there.

I don't know if this is possible, but it would be nice if behind the scenes, nvQuickSite:

1. Determines if the current site might be a localhost site (e.g., not .com or other TLD).
2. If this might be a localhost domain, look for a localhost/IIS express certificate.
3. If a localhost certificate is found, the SSL binding is added using it.

This would save me time from:

1. Forgetting this doesn't happen with my nvQuickSite instances,
2. Get confused for a moment. 😕
3. Remember this site doesn't have SSL applied. 🤦🏽‍♂️
4. Get annoyed and 🙄 at myself.
5. Go into IIS and manually apply the SSL binding. 🌎 🔐