So, we close feature requests we won't address and assign features we might address to the Under Review label. But keeping the issues open would reduce community visibility into the actual status of a feature. Technically, we could keep all feature requests open forever. Troubleshoot and create logs for MSBuild problemsįeature suggestions, are a means of communication between us and the members of the developer community.
#Devslopes community how to
![devslopes community devslopes community](https://i.ytimg.com/vi/1dl91ORwmy8/hqdefault.jpg)
Here are some common places to file those issues: When that happens, we'll close the issue and ask you to open it with the other product.
![devslopes community devslopes community](https://miro.medium.com/max/12776/1*sX121vVfBVT5RGRiepETiA.jpeg)
It could be another related application or an extension. Sometimes when reporting an issue, it turns out to be caused by another product and not Visual Studio. After that, we close the ticket after 14 days of inactivity. If we don't receive the information within seven days, then we send you a reminder. We comment on the issue with the specific information we need, and you'll receive an email notification. When an issue is missing important information, we assign the Needs More Info state. At this point, we may ask you for further information. If an issue was closed and you feel the reason we gave isn't satisfying, then you can clarify your use-case and request the issue to be re-activated for another pass. We've all been there, whether in this project or others we've contributed to. We understand this may be disappointing if you've taken the time to send us an issue report. Some are too expensive to fix, some might regress other feature areas, and some may have too low an impact. Track the progress of your problem reports by referencing the Problem states and FAQ. As Visual Studio product teams review your feedback, they set it with an appropriate state. For example, after triage you know if we plan to fix your issue or wait for more community feedback.Īfter you report a problem, states indicate where your submissions are in their lifecycle. The goal of triaging is providing you with a clear understanding of what will happen to your issue. Triaging usually takes one week but may take longer. Triaging an issue is a multi-step process that is collaboratively done within the feature team.
#Devslopes community code
Simplify your code around the issue so we can better isolate the problem.Įven with issues that include rich details, we may be unable to reproduce the issue and may ask for more information! Managing problem reports.If you find the issue is caused by an extension you've installed, file an issue on the extension respectively. Recreate the issue after disabling all extensions.If so, vote up the existing issue, providing additional comments or clarifications as needed. Search to see if there exists a duplicate.As appropriate, a code snippet that demonstrates the issue or a link to a code repository we can easily pull down onto our machine to recreate the issue.Images and animations illustrate repro-steps but don't replace them. Images, animations, or a link to a video.3.) and what you expected versus what you experienced. Include the following steps with each issue. The more information you can provide, the easier it will be for us to reproduce and fix your issue. Many issues look similar but have different causes, which makes it harder for us to diagnose your issue. Don't add your issue as a comment to an existing issue unless it's for the identical input.Combining multiple problems or feature requests into a single issue makes it harder for us to diagnose, and harder for other users to vote for your issue.Writing a good bug report or feature suggestionįile only one problem or feature request per issue. If you can't find an existing issue that describes your bug or feature, submit an issue using the guidelines below. We have customer support staff monitoring that tag and will help answer the questions. If your issue is a question, ask the community on Stack Overflow using the tag visual-studio. If you find your issue already exists, make relevant comments and cast your vote. Search for your issue on Visual Studio Developer Community to ensure it doesn't already exist. The Visual Studio Developer Community tracks issues and feature suggestions for Visual Studio. The Developer Community tracks issues and feature suggestions for Visual Studio.
![devslopes community devslopes community](https://miro.medium.com/max/1200/1*sX121vVfBVT5RGRiepETiA.jpeg)
#Devslopes community for mac
Applies to: Visual Studio Visual Studio for Mac Visual Studio Code