MonoTouch MKMapView Zoom Level

I needed to implement  a zoom level similar to Google Maps style for MonoTouch iOS and lucky me after doing little search on the web I found this article written by Troy. This is exactly what I was looking for except it was in Objective-C.

So with my little knowledge of Objective-C I copied his code and converted this to C# for using MonoTouch library. I hope this code snippet will help other monoTouch coders as well. Also a big thanks to Troy for such a nice article.

[gist /]

In order to use this copy the class to your project and update the namespace. Then in your XIB file, drop a regular MKMapView control and setup all the property you need. Then change the class name to MKMapViewZoomLevel (as is our custom class name).





ASP.NET MVC – Binding to Dictionary

Today I came across a situation where I had a display a list of combo boxes inside a part of a complicated tab based form. The model of the view was a different object then this particular section I was trying to render. I had a different controller action to do the updates.

After googling I came across this article from Scott ASP.NET Wire Format for Model Binding to Arrays, Lists, Collections, Dictionaries which turned out to be very helpful.

While implementing this all I need the binder to return something like a dictionary of int key with int value.

public ActionResult EditProjectAccess(int? id, Dictionary<intint> ProjectAccess)

So in my View I used the following snippet:

Var counter = 0;
foreach (var item in ProductGroups)
(var pj



        @Html.Hidden(“ProjectAccess[” + counter + “].key”, pj.ProductId)
        @(Html.DropDownList(“ProjectAccess[” + counter + “].value”new SelectList(new List<Object>{
          new { value = “0” , text = “No Access”  },
          new { value = “1” , text = “Participant” },
          }, “value”“text”, pj.HasAccess(Model.ResourceId)?0:1)))



The key here was using the Hidden field for storing the key name, and the combo box for the value field. One thing though the counter values should be incremental, i.e. no gaps in sequence. Else on the model you will only get up to the sequenced item.

So now I can easily get access to my dictionary list and figure what each of those combo was values was selected to. The key can be string as well and the value can be complex object. Just follow Scott’s blog article.