![]() Business Intelligence Development Studio is hosted on Microsoft's project hosting website GitHub. ![]() It is based on the Microsoft Visual Studio development environment, but customized with the SQL Server services-specific extensions and project types, including tools, controls and projects for reports, ETL dataflows, OLAP cubes and data mining structure.īIDS functionality can be augmented with BI Developer Extensions (previously known as BIDS Helper), a Visual Studio add-in with features that extended and enhance business intelligence development functionality in SQL Server 2005, 2008, and 2008 R2 BI Development Studio (BIDS) and SQL Server 2012 SQL Server Data Tools (SSDT). It would be so much easier to do all that using GIT and then merging the final changes back into TFS.Business Intelligence Development Studio Developer(s)īusiness Intelligence Development Studio ( BIDS) is the former IDE from Microsoft, and was used to develop data analysis and business intelligence solutions utilizing Microsoft SQL Server Analysis Services, Reporting Services and Integration Services. The feature request ticket is a great place to share your comments and thoughts, so make sure to vote and comment there as well.ĭo you like the idea of community experiments like this one? Let us know in the comments below.įor those unfortunate people like me who have to use TFS, could you also add a setting to make it so that all Visual Studio instances share the same view of TFS Included and Excluded changes, one of the problems of having multiple Visual Studios open is that if you accidentally submit from the wrong instance of Visual Studio you can find yourself checking in files that weren’t meant to be part of the final changelist.Īlso it would be really good if there was a feature to automatically create a GIT Branch of the current state of a set of folders, so that you could iterate on to create a new feature and then once you were finished commit those changes back into the TFS view of the source.Īs currently you can only check against the previous checked in state of the files, when often you might want to do a diff against the last time you reached a milestone, but all you can do as add one more shelf set. Make sure to share any ideas and bugs on the GitHub issue tracker, and feel free to send pull requests too. If this feature is interesting to you, please install the Solution Colors extensions and take it for a ride. Find it under Environment -> Fonts and Colors -> Solution Colors.īoth built in and custom themes are not affected by this colorization. You can adjust the thickness of the line from the Tools -> Options dialog to suit your liking. It works for both solutions and for folder-based workspaces (CMake, etc.). Select None from the list to remove it again. ![]() The way it works is that you manually assign a color to a solution, by right-clicking the top tree node in Solution Explorer.Įvery time you open that solution, the extension applies the color automatically. Getting startedĪfter installing the extension, you are ready to start colorizing Visual Studio. We call it Solution Colors and the first iteration puts a 3-pixel thick colored line above the status bar (see image above). We’re starting out with an extension to kick off the experiment. Let’s experiment and keep iterating to find the best solution together. ![]() Instead, we may need a different UI paradigm and colorization scheme. An experimentĭue to the UI differences in Visual Studio Code, it may not be desirable to port Peacock as is to Visual Studio. A feature request on the Visual Studio Developer Community is gaining steam asking for the same feature be added to Visual Studio, so please vote and comment if you’re interested. ![]() The Peacock extension for Visual Studio Code does exactly that, and with 1.7 million installs it appears to be working great for lots of developers. What if each instance could have a unique color so you could instantly tell them apart? Would you use it? Especially if you’re working on different branches of the same solution, which makes them look almost identical. When you have multiple instances of Visual Studio open at the same time, it can be tricky to tell them apart. ![]()
0 Comments
Leave a Reply. |