When running automatic tests, Assert.Inconclusive causes an error (RED icon) in Visual Studio 2012.
In previous versions it caused a warning (YELLOW icon), so that I could easily distinguish inconclusive tests from failed tests. I consider this as a a regression.
Note that for me "inconclusive" means: "the test has an important prerequisite that wasn't satisfied, so I could not run this tests", this must NOT be an error, but a warning to me to apply the prerequisite.
Consider that I don't use the testing features of VS only for unit tests, but also to automate more complex integration tests that sometimes involve files and the database. On some test machines I cannot apply some prerequisites, and I know it, so I often don't care if some tests are "Inconclusive", but I want to spot the ACTUAL failures immediately.