Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, February 9, 2018 5:45 PM | 1 vote
If you happen to open some random solution that doesn't have anything git related and that random solution files are readonly you'll be getting these dump questions from visaul studio:
It's most annoying when you try to convert some old read-only solution to VS2015 format. Most of the the suggestions if you google for the problem is surprisingly to disable git source control! What a fail with just a dumb decision to show a message box.
Visual studio already has an option "allow editing readonly files and warn when attempt to save" in options. Please, KILL THIS MESSAGE BOX!!
All replies (2)
Monday, February 12, 2018 5:42 AM
Hi ppsmtl，
Thanks for your feedback, it was related to the Git plug-in which has been proved..
As you said that the workaround is that we need to disable this plug-in now:
Tools -> Options -> Source Control, change "Current source control plug-in" from "Git" to "None". But this will close the current project and/or solution.
Since the previous connect/feedback report for old products has been retired, if possible, you could choose the new way here:
/en-us/collaborate/connect-redirect
Since the latest version is VS2017, if you have the latest Environment, you could test it and check that whether it still has this issue, if it still has this issue, you could report it to the VS2017 developer community site directly though the VS IDE:
https://developercommunity.visualstudio.com/spaces/8/index.html
Sincerely,
Jack
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Monday, February 19, 2018 3:50 AM
Hi ppsmtl，
What about this issue? Please also feel free to post your latest progress here.
Best Regards,
Jack
MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].