Now I’m a fan of Ninject (http://ninject.org) an inversion of control dependency injection container, and a fan of ASP.NET MVC (http://asp.net), so in order to use Ninject and MVC 3 you can use NuGet to setup it for you.

To do this run the following package install command in the Package Installer:

install-package ninject.mvc3

What’s really neat about NuGet is that it will also install any dependencies, so in this case will also install Ninject itself.

The solution seems to be that the framework for the project is set to ‘.NET Framework 4 Client Profile’, while what it needs is ‘.NET Framework 4′.  You can change this in the project properties page.

It seems to be something to do with System.Web, but haven’t narrowed it down more than that.

The option is  available from the right-click menu on the Solution:

Which opens a dialogue allowing you to pick which projects to start:

'Could not load file or assembly xxxxxx or one of its dependencies. An attempt was made to load a program with an incorrect format.'

The reason for this is the Appliction Pool in IIS is not allowing 32-bit application to run.

You can fix this in IIS Manager by selecting the Application Pool and opening the Advanced Settings dialogue, link on the right of the IIS Manager:

 You can then toggle the option for 32-bit applications:

For example, you can use standard .NET formatting such as currency and date:

<TextBlock Text="{Binding Amount, StringFormat={}{0:C}}"/>
<TextBlock Text="{Binding Date, StringFormat={}{0:dd/MM/yyyy}}"/>

The empty {} after the StringFormat= escapes the text before the formatting string.

You can add text in front of the formatting string too, e.g.
StringFormat=Amount: {0:C}
in which case you don’t need to escape the string with the {}.

More advanced formatting options can be acheived using a multi-binding, for example:

<TextBlock>
  <TextBlock.Text>
    <MultiBinding StringFormat="Date {0} Time {1}">
      <Binding Path="DueDate" />
      <Binding Path="DueTime" />
    </MultiBinding>
  </TextBlock.Text>
</TextBlock>

However, there are occasions when you want to hide methods from external consumers for good reason, but still need to unit test them.  For example, producing a library to distribute to third-parties.

To do this with .NET you can mark the assembly with InternalsVisibleTo and specifiy the public key of the project allowed to view your internals.

For example, I have a project called MyNewProject and a project containing units tests for this called MyNewProjectTests, I can add the following code to the assembly.cs file in MyNewProject with the public key of the test project:

[assembly: InternalsVisibleTo("MyNewProject, PublicKey=0024...")]

Note, I’ve not included the entire public key here.

Now the internal methods are visible to the test project we have one more task. The unit test frameworks Rhino Mocks and Moq use a proxy class called DynamicProxyGenAssembly2 to represent your object when testing. We therefore need to expose the internals to this class also. We do this in the same way with another entry in the assembly.cs file:

[assembly: InternalsVisibleTo("DynamicProxyGenAssembly2, PublicKey=0024")]

<EditText
...
android:singleLine="true"
android:inputType="numberDecimal"
...
>

Then use, for example, Double.parseDouble(…) to retrieve the value in code.

Incidentally, the documentation recommends avoiding floats and using double instead.

...res\layout\main.out.xml:1: error: Error parsing XML: no element found

This occurs when you try and run the application from the main.xml layout file. The application cannot run from here and needs to be run from the java file.

The answer is to ensure that a java file is selected when you hit run, as you should run the java not the xml file.  The easiest way to ensure you don’t do this is to use the Run History options in Eclipse.

AddressAccessDeniedException

with the error message

HTTP could not register URL http://+:80/. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details)

The Microsoft site (http://go.microsoft.com/fwlink/?LinkId=70353) does have a solution to the problem using httpcfg and netsh. However the far simpler solution is to run Visual Studio as Administrator

You can do that by right-clicking the shortcut for Visual Studio and selecting Run as adminstrator, or to permanently run as Administrator, right-click and select Properties. Find the Compatibility tab and check the Run this program as administrator checkbo€x.

public byte[] imageToByteArray(Image imageIn)
{
    MemoryStream ms = new MemoryStream();
    imageIn.Save(ms,System.Drawing.Imaging.ImageFormat.Gif);
    return ms.ToArray();
}
and conversely, turning a byte array into an image:

public Image byteArrayToImage(byte[] byteArrayIn)
{
    MemoryStream ms = new MemoryStream(byteArrayIn);
    Image returnImage = Image.FromStream(ms);
    return returnImage;
}