I really like the @Html.EditorFor(m => m.Foo) expressions and such.
There are a few issues though,
1. Refactoring the Model does not refactor the CSHTML (I am actively working on the model so its a big issue)
2. Rebuilding does not build the CSHTML files to tell me that it no longer compiles. This becomes a runtime error.
3. IdFor gets the Id of an EditorFor form field. I used that in a "var foo = $('#@Html.IdFor(m => m.Foo)');" but at that point it becomes nasty. Ideas?
This was pure greed on Microsofts part. WD/Seagate just ######ing went along with it, knowing theyd make bank. It took me a long time to buy an XSX for this sole reason. And honestly? I wish I hadnt supported this. But I didnt want to have to re purchase my whole library either. Lose, lose for consumers.
So, you do know the truth about Don TACO?!
You didn't back up any of your claims except that a prosecutor said that Biden is a 'well-meaning, elderly man with a poor memory'...at 82 years old. Ahem.
Question
+Red King Subscriber²
I really like the @Html.EditorFor(m => m.Foo) expressions and such.
There are a few issues though,
1. Refactoring the Model does not refactor the CSHTML (I am actively working on the model so its a big issue)
2. Rebuilding does not build the CSHTML files to tell me that it no longer compiles. This becomes a runtime error.
3. IdFor gets the Id of an EditorFor form field. I used that in a "var foo = $('#@Html.IdFor(m => m.Foo)');" but at that point it becomes nasty. Ideas?
Link to comment
https://www.neowin.net/forum/topic/1248318-aspnet-mvc5-cshtml-razor-issues/Share on other sites
5 answers to this question
Recommended Posts