For a project on the side I’m creating a Web API which has to parse XML requests in a POST. The first method I’ve written looks like this:
On some installations of Visual Studio 2010, 2012 or 2013 I’m confronted with strange behavior. One of these strange things are the black lines in the Watch Window of Visual Studio. Just like the screenshot below (this isn’t my screenshot, I’ve ‘borrowed’ it from someone else)
There comes a time when you have to do something which appears impossible at start. One of the things I had to confront is moving my SQL database files from the D-drive to the L-drive.
Windows 8 has given us a lot of new and cool features for both developers and users. One of these features is the possibility to pin websites to your start screen. Default this tile will look like the favicon of the website, but you are also able to change the pinned tile to a live tile. The live tile will get the necessary information from the RSS feed of the website.
For some time now I’ve been in possession of the Sony PRS-T1 e-reader. E-readers are great devices and I find it much easier to read from an e-ink screen compared to a regular tablet screen.
Some time ago Microsoft has introduced the ASP.NET Web API framework. It’s a framework you can use to create your own RESTful services. It’s much like WCF Data Services or WCF RIA Services, but a lot easier to use (IMO). I’ve never liked the WCF-stack much, probably because configuring it always posed to be a hassle.
The solutions in the project I’m working on are quite big and can easily take up 30 to 90 seconds to build, even though we have rather fast laptops. This is probably because of some build-plugins we are forced to use and the tight SharePoint integration of those plugins. Nevertheless, it’s quite annoying to see Visual Studio ‘hang’ every time you build your solution.
When setting up an Orchard website you’re given a choice to use a ‘normal’ SQL database, or SQL Compact. When developing new modules I often choose for the SQL Compact option. I choose this option, because it’s very easy to backup and restore the database file. If you mess something up, you’re fairly safe.
You can of course backup and restore normal SQL databases, but this takes a bit more effort compared to copy-pasting a database file.
All of a sudden all my websites didn’t work anymore. Using some common sense in searching for the root of the problem I discovered the IIS Admin Service hadn’t started after booting up my machine. Trying to manually start up the service didn’t help much either, I was confronted with a message telling me “The system cannot find the file specified.”. Sadly, the event logs didn’t help much, as the logs told me about the same “The IIS Admin service terminated with the following error. The system cannot find the file specified”.
Some time ago my ForeFront TMG server had crashed and not being an expert sysadmin, I wasn’t able to figure out what was wrong. The only thing I could think of was restoring the server from an earlier snapshot. Thanks to the Hyper-V interface this is really easy, even a software developer can do this.