Tagged: Visual Studio

Getting Started with Containers for ASP.NET Developers on Windows

worksonmymachineContainers give you a way to run you application in a controlled environment, isolated from other applications running on the machine and from the underlying infrastructure.

It means that when you go to deploy, all the dependencies are published together. So you can finally say, “It worked on my machine” and mean it. All the dependencies with the same versions in your container will be there when you deploy to the cloud.

Continue reading

‘Exited with code 9009’ publishing .NET Core app to Azure Websites

imageI recently installed a fresh copy of Visual Studio 2017 on a new computer. And I am migrating some code from .NET 4.6 to .NET Core. After some hair pulling over changes in the libraries, it now compiles and runs great.

But when I go to deploy to Azure Websites I get errors that look like this:

The command "bower install" exited with code 9009.

OR

The command "npm install" exited with code 9009.

So what is Bower, and Gulp and why are they interesting in a code migration?
Continue reading

Snippet – Setting MIME Types (Font Awesome or Custom Fonts or Json File Extensions Doesn’t Work When Deployed on Windows)

imageWhen using custom fonts on Windows Azure, users have reported issues. For example, Font Awesome icons would not display. Or even if the fonts do display, it might not display correctly on some devices, such as Windows Phones.

In other cases, you may have a file type that does not map to the right MIME type.

In fact, I exposed most of the JSON files with the .txt extension just to avoid the issue of IIS not serving up .JSON files as expected.

It turns out — the issue is that IIS 7 – 8.1 serves up the wrong MIME type for web font files. So you need to be sure the right MIME types are being served up for your font files, as shown here: Proper MIME type for fonts.

When deploying to an IIS servers you need to add MIME support.

Continue reading