I had a tidy-up and spring clean of my home office yesterday, and I cleared a lot of books of my shelves. Before they go to the tip for recycling, here's a list of what I cleared. If anyone wants any of these, let me know by 18th April. A Programmers Introduction to C#, Eric Gunnerson Visual C# Language Reference Programming ASP.NET 2.0 Advanced Topics 2005 Ed, Dino Esposito Debugging .NET 2.0 Apps, John Robbins Javascript: The Definitive Guide 4th Ed, David Flanagan ASP.NET 2.0 Cookbook, Geoffrey LeBlond Essential ASP.NET 2.0, Fritz Onion nHibernate in Action, Pierre Kuate ASP.NET 2.0 Server Control & Component Development, Shahram Khosravi The Definitive Guide to The Microsoft Enterprise Library, Keenan Newton ASP.NET 2.0 Anthology, Jeff Atwood ADO.NET & ADO Examples and Best Practices, Bill Vaughn Pro ASP.NET MVC 1.0, Scott Hanselman Building a Web 2.0 Portal w/ASP.NET 3.5, Omar Al-Zabir Designing and Developing Web-Based Applications Using the .NET Framework, Mike Snell Distributed .NET Programming in VB.NET, Tom Barnaby Applied ADO.NET, Mahesh Chand Developing ASP.NET Server Controls & Components, Nikhil Kothari Enterprise Development with Visual Studio.NET, UML & MSF, John Erik Hansen Inside VS.NET 2003, Brian Johnson
Thought I should write about a problem I ran into last month in the hope that it saves someone else some heartache (or potentially someone tells me how to fix it...) A few weeks ago, while I was searching for something else in Visual Studio's Settings, I ran across this option:
I run on 64-bit Windows, so I figured this would be a sensible option to set and switched it on. And all was good in the world. Until I started on a new project a couple of weeks later, that is, when running it up for the first time I was puzzled to see this YSOD:
Invalid program? What the hell's that coming from? The only thing that I could immediately think of was that the last thing I did before hitting F5 was to install Ninject. I cast around for an hour or so trying assorted types of restarting processes/PCs etc, before going to Twitter...
With #ninject, has anyone seen this error? 'Common Language Runtime detected an invalid program.' More importantly, anyone know how 2 fixit
— Phil Pursglove (@philpursglove) January 20, 2014
@philpursglove ... yes, but I cant remember the details. Sounds a bit like a 32bit app/dll trying to reference a 64bit dll?
— Fran Hoey (@franhoey) January 20, 2014
And yep, as soon as I turned off 64-bit IIS Express the world righted itself... So I'm interested to know what causes this and whether there's a way to successfully run Ninject in 64-bit code (I'm quite prepared for this to be something related to my inexperience with Ninject).