You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MyNamespace.Views.StudentViewModel.
locate to:
MyNamespace.Views.StudentView.
locate with context (Details):
MyNamespace.Views.Student.Details.
It just work with a string 'Details', so why use object type?
A question that was raised a long time ago: It pollutes the name definition.
I must def a namespace like 'xxx.Student.xxx'. But I also have a model named 'xxx.Student.cs'. It's weird to reference members. 'Student' is a class, and also is namespace.
The text was updated successfully, but these errors were encountered:
MyNamespace.Views.StudentViewModel.
locate to:
MyNamespace.Views.StudentView.
locate with context (Details):
MyNamespace.Views.Student.Details.
It just work with a string 'Details', so why use object type?
A question that was raised a long time ago: It pollutes the name definition.
I must def a namespace like 'xxx.Student.xxx'. But I also have a model named 'xxx.Student.cs'. It's weird to reference members. 'Student' is a class, and also is namespace.
The text was updated successfully, but these errors were encountered: