C# Is it a bad idea to create a ViewModel as a controller's field?

Question

Would it be a bad idea to put a view model as a controller\'s field?
So that in each of the action methods I would not need to keep on instantiating it with
C