There have been several solutions offered for this problem and maybe I
missed the following solution or maybe it's frowned upon, but I would
like your opinions.

I was testing various ways to pass the ID of a document and used the
traditional form of a named parameter with Url.Encode() and was able
to pass the ID with very little effort and it was decoded with no
extra work on my part in the controller action.

Is this an acceptable practice or are there some hidden issues that I
am unaware of?

Thanks
Scott

The ToIntId() extension method is your friend:

public static int ToIntId(this string id)
                {
                        return int.Parse(id.Substring(id.LastIndexOf('/') + 1));
                }

                public static long ToLongId(this string id)
                {
                        return long.Parse(id.Substring(id.LastIndexOf('/') + 1));
                }

This serves me well in a a lot of cases. Just use it when you're passing
values to your ViewModel and use the int/long in your ViewModel.

Em domingo, 6 de maio de 2012 09h18min36s UTC-3, Itamar Syn-Hershko
escreveu:

I hadn't thought of having a string ID on the domain model and an int
ID on the viewmodel but that makes perfect sense.

I can just use AutoMapper to map back and forth between the two models
using an IValueResolver class.

I have just started testing different scenarios with RavenDB but it's
been a lot of fun learning a NEW way to work with classes and
persisting data.

A big thanks to the RavenDB crew!

Scott

On May 6, 8:27 am, Felipe Leusin <felipe.leu...@gmail.com> wrote: