This repository was archived by the owner on Dec 19, 2018. It is now read-only.
TModel placeholder at design time causes errors when @model isn't fully qualified #1222
Comments
|
Go ahead and fix this one 👍 |
NTaylorMullen
added a commit
that referenced
this issue
Apr 14, 2017
- Prior to this TModel would be set to a potentially non-fully qualified name. This would cause errors in default MVC templates. - Regenerated test files to reflect new TModel. - Updated unit test to reflect new behavior. #1222
NTaylorMullen
added a commit
that referenced
this issue
Apr 14, 2017
- Prior to this TModel would be set to a potentially non-fully qualified name. This would cause errors in default MVC templates. - Regenerated test files to reflect new TModel. - Updated unit test to reflect new behavior. #1222
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For
@model LoginViewModelwe generateusing TModel = LoginViewModel. This is invalid, the type has to be fully qualified in the using statement but not in the model statement. Instead we should have theTModelalways use System.Object.The text was updated successfully, but these errors were encountered: