When would you not use a strongly-typed ASP.NET MVC view?

Question

Assuming that an ASP.NET MVC View is going to show data, is there any scenario where you would not want to use a strongly-typed view?

Answer 1

Places where there is no model -- like Logon/Logoff.

Answer 2

I think that you should follow the practice of always using strongly typed views, unless no model isused at all like previously mentioned for pages like login.

Answer 3

I'm forced to put some data in layout. Cause I couldn't find any good way to make strongly typed layout, I'm passing necessary data through controller base class and picking it up at layout through indexer of viewData by key.

For partialviews i just nest form models, no problems there i guess.