> 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

> What controller action are we talking about? Basically you want to keep
> most of them, at least the more common, human readable, and encoding
> doesn't really help

> See the "Routes" section in  
> http://ravendb.net/kb/3/using-ravendb-in-an-asp-net-mvc-website

> On Sun, May 6, 2012 at 3:12 PM, scott <pfaff.sc...@gmail.com> wrote:

>> I have read several posts on this forum regarding RavenDB and it's
>> default style of document ID's i.e. "Countries/1" and how they
>> conflict with embedded query string parameters in a URL.

>> 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

> 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.