Would I be beaten with the "anti-MVC" stick to suggest this?
(OrderSummary.cshtml - on the checkbox, just add jquery onclick to click the updatecart button)
<input id="removefromcart" type="checkbox" name="removefromcart" value="@(item.Id)" onclick="$('#updatecart').click();"/>
(EDIT: I haven't tried your method - what would happen if the customer changed a qty on another line, and then clicked the remove button on a different line? I'd think he'd lose his qty change.)
(OrderSummary.cshtml - on the checkbox, just add jquery onclick to click the updatecart button)
<input id="removefromcart" type="checkbox" name="removefromcart" value="@(item.Id)" onclick="$('#updatecart').click();"/>
(EDIT: I haven't tried your method - what would happen if the customer changed a qty on another line, and then clicked the remove button on a different line? I'd think he'd lose his qty change.)
You're correct "New York" just rendering an anchor tag would cause the loss of data when clicked. Ciwan could make the method I provided an ajax call without trouble. The method you've provided above would fall victim to a similar problem to my original suggestion. Instead of updating one row you're actually updating the entire cart, and from a user perspective that would feel pretty awkward if a "remove icon" updated seemingly unrelated rows.
There are many ways to approach the issue described above and each have their drawbacks. Thanks for the alternate solution!