http:\/\/visualstudio.uservoice.com\/forums\/121579-visual-studio\/suggestions\/2302594-automatically-fix-fixable-errors<\/a><\/p>\nSuggestion text after the break.
\n<\/p>\n
I suggest you… automatically fix fixable errors<\/p>\n
Some errors in the error list could be automatically fixed. For instance, you build your code and the error “The type ‘bla’ is not referenced. You must add a reference to assembly ‘System.Data.Entity'” appears in the error pane. This error is easily fixed by adding the correct reference to the project, but since Studio already knows what it’s looking for, it knows where it’s located (GAC), why isn’t there an option to fix it?<\/p>\n
It would be nice if the error pane would have a column “Autoresolve” with for each error which migh be fixable a link “Try resolving”. Studio would then try to autoresolve the problem, for instance by adding the correct reference to the project and all would be well. If there was a problem resolving the problem, Studio could display an error message telling the user the autofix didn’t work and he should correct the problem himself.<\/p>\n
In the same category, auto fixes could be applied for things like missing\/extra parentheses, ; characters, etc. etc. I think the list of autoresolvable things is actually pretty long.<\/p>\n
But please note: VS should NEVER do this on it’s own. It should always be the developers action to perform an autoresolve.<\/p>\n","protected":false},"excerpt":{"rendered":"
This weekend I added a suggestion for a new simple but powerfull feature in the next version of Visual Studio. In my opinion it’s a pretty good one (otherwhise I wouldn’t have posted it anyway), so I thought perhaps you agree on this. Feel free to vote and help me get this one up there.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","jetpack_publicize_message":"","jetpack_is_tweetstorm":false,"jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[34],"tags":[40,39,41,42],"jetpack_publicize_connections":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p3KFR1-5U","_links":{"self":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/posts\/366"}],"collection":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/comments?post=366"}],"version-history":[{"count":0,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/posts\/366\/revisions"}],"wp:attachment":[{"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/media?parent=366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/categories?post=366"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/blog.repsaj.nl\/index.php\/wp-json\/wp\/v2\/tags?post=366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}