Update dotnet.md

[Rick-Anderson]

This took a long time to find when using Down.

Per MS style guide avoid parenthetical expressions (they're hard to read in English (and impossible (nearly) to MT (Machine Translate))) :)

[ajcvickers]

@bricelam Is this change correct? Removing a migration doesn't cause Down to be called, does it?

[bricelam]

This part isn't correct:

Removes...by calling the Down method

We only execute the operations described in the Down method if the user tells us to. (By confirmation or by specifying --force) And, it's not related to rolling back the code changes.

[roji]

Sorry, I was focusing on the language here and missed this.

Submitted #3156 to fix this, @bricelam is that correct?

FWIW I know we've discussed this before, though I still find it odd for --force to do something different from what the command does without it (with it we touch the database, without it we don't). From my Unix mindset, --force is supposed to do the exact same thing, just to force the tool to complete silently without aborting on risky situations. Hopefully I'm not still misunderstanding.

[bricelam]

--force will skip checking the database. This might in turn skip reverting the migration. But we also warn during --force that you might have to manually revert the database if the migration was applied. In other words, --force avoids some built-in guardrails that might be preventing you from removing the C# code for the migrations.