Asp.Net Error: There is no build provider registered for the extension ‘.html’

When you try to map an html file in ASP.net and rewrite the URL to remove .html extension such as the example below routes.MapPageRoute(“myhtml”, “myhtml”, “~/Resources/demo/myhtml.html”); It throws an error as following There is no build provider registered for the extension ‘.html’. You can register one in the <compilation><buildProviders> section in machine.config or web.config The following configuration changes in web.config fixes it. <compilation debug=”true” targetFramework=”4.5″ > <buildProviders > <add extension=”.htm” type=”System.Web.Compilation.PageBuildProvider” /> <add extension=”.html” type=”System.Web.Compilation.PageBuildProvider”/> </buildProviders> </compilation>  

Cordova Plugins: Review Unnecessary Permissions

If you went through the article on adding social sharing feature in HTML5 game using Intel XDK, it seemed like a simple plugin which should not require any permission but after adding the plugin and few more other plugins I found that WRITE_EXTERNAL_STORAGE permission was added in my android app so I checked all plugins one by one to see which plugin is adding what permissions and found out that WRITE_EXTERNAL_STORAGE permission was being added by social sharing plugin. When I checked developer notes (quoted below) I found that the permission was not required in my case, since I was not fetching any remote images for sharing. For sharing remote images (or other files) on Android, the file needs to be stored locally first, so add this permission to AndroidManifest.xml: <uses-permission android:name=“android.permission.WRITE_EXTERNAL_STORAGE“ /> In fact it was just a simple play store URL which I was sharing in my app so[…]

WordPress Error: Briefly unavailable for scheduled maintenance. Check back in a minute

This error occurs when you try to update something in WordPress site and the update fails for some reason and then your site goes down and following message is displayed Don’t worry. The process to fix this is pretty straight-forward. Go to your blog installation folder and look for .maintenance file. This file is generated by WordPress when the update occurs and then removed after the update finishes. In case update fails and this file could not be removed, then the above error message is displayed. Delete this file and you will be back up.