After almost 3 years with mvc I'm scratching my head. Is it just me, or does the way we specify links in asp .net mvc suck?

@Html.ActionLink("Log Off", "LogOff", "Account")

In the previews for mvc 1 we had the funky generic action links which gave us intellisense and compile checking, which I LOVED. I know they removed them because of performance issues and because you could not actually guarantee that the route would resolve all the time... However the default way of doing it just doesn't make me feel safe enough in a big application.

I've also used T4Mvc with MVC2, to be honest, I didn't really like it. It's not part of the Mvc framework and frustrating to develop with especially with source control in big teams and continuous integration builds.

I guess I could also import Mvc Futures and keep using the generic types (it's probably what I'll do).

I'm just about to start a very big project and was wondering what other people are thinking? Is anyone else annoyed with the options or has a new solution?

It seems like ActionLinks are the most basic & frequently used feature. Shouldn't there be a good out of the box solution, we're just about to hit revision 3 of this framework.