Skip to main content

Allow the download of Windows Phone XAP files within IIS (avoiding 404 errors)

Some months ago I made a couple posts explaining how we can configure IIS to allow the download of Android APK and iOS IPA files:  now, upon request, I’m posting the same thing for Windows Phone XAP files.

When you’re developing a Windows Phone App you’ll most likely want to give someone – the customers and/or beta-testers, colleagues, etc – an URL pointing to a .xap file containing the efforts of your hard work, which is not (yet) present in the Windows Store. Since the vast majority of web servers (including IIS) don’t natively support the .xap MIME-type, your URL will most likely give an apparently odd 404 – Page Not Found error response. In order to overcome the problem you need to add the proper MIME-type corresponding to the .xap file in the following way:

  • Open the IIS Administration Panel (see picture).
  • In the left panel, click to the entry corresponding to your global IIS instance (pt. 1 in picture) so that each modification you’ll make will be applied to all your past, present and future web-sites. If you only want to handle the .apk MIME-type for a specific web site, click to the entry corresponding to it instead.
  • In the right panel, Click to the “MIME Types” icon. You will be presented with a listing of all currently supported MIME-types.
  • Click to the “Add…” button near the top-right corner (pt. 2 in picture) and add the following MIME-type (pt. 3 in picture):
    • Extension: .xap (be sure to include the dot)
    • MIME-type: application/octet-stream

ipa-mime-type-iis

(click over the picture to enlarge)

Needless to say, this can be used to allow the download of any other file extension.

If you’re not using the IIS Management interface and/or if you want to work directly on web.config level you can achieve the same result by following the comprehensive instruction explained in the official IIS configuration page.

CS:GO Video Making Tutorial from DEMO / Replay Files – Part 2 of 3

This tutorial, split into three parts, explains how to release a FullHD, 60fps Youtube-ready video from one or more CS:GO Demo / Replay Files.

In the Part 1 we talked about hardware and software requirements, explained how to properly configure the environment in order to obtain a consistant, top-notch quality raw recording of a specific game action sequence made of a single WAV file and a vast amount – 1 for each frame – of uncompressed TGA  files. In this Part 2 we’ll learn how to convert these recordings into single AVI files and how to import them into a video-editing software such as Sony Vegas. Eventually, in the Part 3, we’ll address some common issues and also see how we can improve this technique by configuring our system in order to save some valuable time for most of the steps.

By following the required steps you’ll be eventually able to create FullHD, ultra-smooth 60fps game videos just like the following one:

 

Read More

CS:GO Video Making Tutorial from DEMO / Replay Files – Part 1 of 3

A while ago I wrote a post about converting CS:GO demo/replay files to AVI using the internal console command  startmovie  and Lagarith Lossless Codec: although that tutorial still a viable way to produce good-looking 30fps movies in a decent fashion, the technique below is most suited if you want to make top-notch movies/montages and upload them on Youtube now that the Youtube player supports native 60 fps playback.

That’s why I made this tutorial, which is basically an updated version of the former one. By following the required steps you’ll be able to create FullHD, ultra-smooth 60fps game videos just like the following one:

To better separate its core concepts the tutorial has been splitted into three sections:

  • Part One will focus on system requirements, CS:GO configuration settings and raw recording techniques in order to obtain a frame-by-frame recording footage (tga + wav) of each video part using the CS:GO spectactor-mode.
  • Part Two will focus on converting each raw footage obtained during Part One into a single high-quality AVI file, importing them into Sony Vegas – or any similar video editing software – to create our project/montage.
  • Part Three will address some common issues, as well as  introduce some process/system optimizations in order to speed-up some steps and save some valuable time.

Read More

Allow the download of IPA files within IIS (avoiding 404 errors)

Some months ago I made a post explaining how we can configure IIS to allow the download of Android APK files: now, upon request, I’m posting the same thing for iOS .ipa files.

When you’re developing an iOS App you’ll most likely want to give someone – the customers and/or beta-testers, colleagues, etc – an URL pointing to an .IPA file containing the efforts of your hard work, which is not (yet) present in the App Store. Since the vast majority of web servers (including IIS) don’t natively support the .ipa MIME-type, your URL will most likely give an apparently odd 404 – Page Not Found error response. In order to overcome the problem you need to add the proper MIME-type corresponding to .ipa file in the following way:

  • Open the IIS Administration Panel (see picture).
  • In the left panel, click to the entry corresponding to your global IIS instance (pt. 1 in picture) so that each modification you’ll make will be applied to all your past, present and future web-sites. If you only want to handle the .apk MIME-type for a specific web site, click to the entry corresponding to it instead.
  • In the right panel, Click to the “MIME Types” icon. You will be presented with a listing of all currently supported MIME-types.
  • Click to the “Add…” button near the top-right corner (pt. 2 in picture) and add the following MIME-type (pt. 3 in picture):
    • Extension: .ipa (be sure to include the dot)
    • MIME-type: application/octet-stream

ipa-mime-type-iis

(click over the picture to enlarge)

Needless to say, this can be used to allow the download of any other file extension.

If you’re not using the IIS Management interface and/or if you want to work directly on web.config level you can achieve the same result by following the comprehensive instruction explained in the official IIS configuration page.

While you’re at it, if you’re willing to do the same thing with  Windows Phone’s .xap files you can check this post and wrap it up aswell.

Close