Michael James - Developer

Last July I wrote a blog post about prototyping getting Entity Framework CodeFirst working with Linq To Lucene . I hadn't realised it was quite that long ago but alas time flies especially with a baby. Anyhow, I never finished the work nor made it "feature" ready or submitted it back to the project, this was partly due to the apparent inactivity. However this week the Linq To Lucene project has become quite active, and as I now need to use the implementation I spent a few hours to finish it. This included working out how to get all the tables off of a DbContext, which involved a bit of reflection magic and then writing some tests to ensure it worked at least how the LinqToSql version had done. I have now submitted this as a patch, http://linqtolucene.codeplex.com/SourceControl/list/patches  - item id 11857, and hope its available in the main trunk soon, enjoy!

Today I had the unfortunate circumstance for VS2010 to crash whilst I was working, nothing to big I thought, I've had this happen before. I reopened VS went to open my solution and got the following message: --------------------------- Microsoft Visual Studio --------------------------- The 'NuGet.Tools.NuGetPackage, NuGet.Tools, Version=1.6.21215.9133, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' package did not load correctly. EEK! Nuget is smegged :( I immediately thought to uninstall the extension and then reinstall it, same thing happened :( I then, (looking back this was foolish as NuGet is shared), thought I know I just load it in VS11 that will work, it also errored. Not cool, the error message however directs you to start VS with logging enabled by using the /log command argument and then to look at the activity log.  The activity log is located in your appdata roaming folder, simply stick %appdata%\Microsoft\VisualStudio\10.0\ActivityLog.xml in...

Introduction So recently I have started a company and been working on a rather large project, initial plans were to use Window 7 or Windows 8 tablets for the "mobile" solution however for various reasons the plan has somewhat changed to now use iPads. As primarily a .Net developer this was a tough decision but a necessary one. However I often talked about using MonoTouch for doing iOS develop after successfully doing some work with MonoDroid when it was in beta. So this is my solution, use MonoTouch to code as much as possible in C# and then Xcode where necessary. I thought it would be a good idea to blog my experiences and any insights I gleam during my first few weeks. I have to admit I have never owned a Mac or an iPad so its all very new, although I have used other peoples. Stage 1 - Order the kit! First things first the kit, as most of my work won't actually be on the iPad application but on Azure services etc I decided that the Mac Mini was the way to go. I...