![]() ![]() Here’s a list of all our past community experiments in case you’re curious. So, thank you and let’s keep experimenting together going forward. What to me really sets these two features apart is the fact you helped design, test, iterate and sign off on them. I’ve shown this feature several times at conferences, and it always receives positive feedback and applaus from the audience. Through the monthlong experiment, 3,000 of you helped us identify edge cases and new scenarios by using the open-source extension Copy Nice. That became clear when we ran the Copy with propery indentation experiment in collaboration with you. We knew there was some interest in this feature but had no idea just how much. This feature idea is several years old and saw the light of day three years ago in the Tweaks extension for Visual Studio 2019. In all its simplicity, it removes the indentation in front of copied code, so when you paste code from Visual Studio into Outlook/Slack/whatever it will look great every single time. ![]() This feature eliminates one of these paper cuts I gave myself daily. You’ve heard the term “death by a thousand paper cuts”, I’m sure. Though this feature has a long and somewhat strange history in Visual Studio, I’m happy it finally made it. I don’t use it every day, but when I need it, I really need it. I’ve used the File Differ extension for years, and I’m incredibly happy to see this now built in. After a month of iterating and collaborating with you, we had the first feature implementation ready. So, we launched an experiment here on this blog to better understand the interest and which of the features were the most important, so we knew where to start. It wasn’t just files, but also selections in the editor, contents of the clipboard, Git branches and a lot more that could be useful to compare. Still, there were different approaches to comparing and diffing. And lots of other IDEs and editors, including our own VS Code, had this feature. Over the years, several extensions exposed the file-diffing command through buttons in the context menu. The only way to use it was from the Command Window ( View -> Other Windows -> Command Window) by typing the command name Tools.DiffFiles and pass in two file names to diff. However, it was never exposed outside Team Explorer. Server Name: Specify the hostname of the server on which you want to shrink the database. Specify the connection parameters as follows: Connection Name: Provide desired connection name. First, we must configure the SQL Server connection. Visual Studio 2012 introduced this feature and used by the Team Explorer tooling for working with TFS. A dialog box named Shrink Database Task opens. This is the story of how they came to be and why they are my favorites. They were both created in deep collaboration with you, the user, and went through multiple iterations before you gave your final thumbs up. Two of my favorite features in Visual Studio happen to share a similar origin story. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |