tag:visualstudio.uservoice.com,2008-02-07:/activity Microsoft on UserVoice 2013-02-15T04:09:08-08:00 tag:visualstudio.uservoice.com,2008-02-07:Event/13400958 2013-02-15T04:09:08-08:00 2013-02-15T04:09:08-08:00 Do not eliminate the CLASSIC view of MSDN [updated] <p>Microsoft is apparently about to eliminate the classic view of MSDN in favor of the poor low-contrast, pale, washed out &#39;lightweight&#39; view. When you visit MSDN now you will see the following if you are viewing the CLASSIC view: &quot;This view of the MSDN and TechNet Libraries will be replaced soon with the Lightweight view. Try it now by clicking the Lightweight link above.&quot; This is more of the same from Microsoft in reducing the developer experience to a shred of what it once was, and makes using MSDN as unpleasant as the grey theme of VS2012. </p><p>Sherry Barber said:<br /><div class="typeset"><p>I agree. We don&#39;t need a different (not better) hammer. The hammer is the tool we use to do our jobs. We don&#39;t want to have to learn how to use a different tool, in addition to having to learn and keep up with rapidly changing technologies. Classic view is our hammer. Please return the classic view.</p></div></p> Sherry Barber tag:visualstudio.uservoice.com,2008-02-07:Event/13400027 2013-02-15T00:50:07-08:00 2013-02-15T00:50:07-08:00 Bring back Macros [updated] <p>I am amazed you&#39;ve decided to remove Macros from Visual Studio. Not only are they useful for general programming, but they&#39;re a great way to be introduced to the Visual Studio APIs. If you are unwilling to put in the development time towards them, please release the source code and let the community maintain it as an extension.</p><p>Richard Broadhurst said:<br /><div class="typeset"><p>Quick macros were one of the best things about the vs editor, although they were getting slower (as was the text editor) with each new vs, they were still the easiest way of re-arranging data (FindNext, forward 2 words, select word, start of line, forward word, paste etc).</p></div></p> Richard Broadhurst tag:visualstudio.uservoice.com,2008-02-07:Event/13400015 2013-02-15T00:46:16-08:00 2013-02-15T00:46:16-08:00 Have official and built-in support for xSpec and BDD framework [updated] <p>The current opensource xSpec and BDD framework available in the market are not well integrated with Visual Studio so I think it is about time there is a built-in support for xSpec framework and BDD from .NET besides the Microsoft Unit Test framework. </p><p>Joshua Partogi said:<br /><div class="typeset"><p>Ideally it is also linked Code Coverage too so I know how much of my code which has been tested by this xSpec framework.</p></div></p> Joshua Partogi tag:visualstudio.uservoice.com,2008-02-07:Event/13399986 2013-02-15T00:38:13-08:00 2013-02-15T00:38:13-08:00 VS11. Bring back the old &quot;Pending Changes&quot; window [updated] <p>The new one is very confusing!!! I think the old one was almost perfect so why did you change it??? I mean, you can add new options but why did you change the philosophy? The most important problems I see with the new one: - No way to have that window independent so it can be accessed easily and fast - Difficult to see at first sight the files changed! (of course, the new “no color” interface is part of the problem...) - Difficult to exclude changes! (in the old one it was so easy by clicking the checkbox...) </p><p>luke.a.page said:<br /><div class="typeset"><p>@Jonathan Stevens, not really I&#39;ve been using this every day for 4 months now. I like some aspects of it, but overall I struggle to say it is better. This needs <br /> a) A way to seperate the window from other tfs stuff - I want to be able to have a window with work items and a pending changes window, not go, oh **** I don&#39;t know the work item, back, back, work items.. 15 clicks later I&#39;ve opened the query, back to pending changes, drag work item in. <br /> b) the concept of showing only some of the changes (e.g. a max of 80 or something and then having a button to see all) is terrible. I want to see all by default but collapsed, not have 2 views <br /> c) I want to be able to switch between a tree view and the only style of a list of changes</p> <p>give me those 3 things and this becomes an improvement.</p></div></p> luke.a.page tag:visualstudio.uservoice.com,2008-02-07:Event/13399943 2013-02-15T00:24:38-08:00 2013-02-15T00:24:38-08:00 Delete project from TFS [updated] <p>I would like to delete a Team Project from Team Server. On the online preview version it seems that this option is not available.</p><p>Joshua Partogi said:<br /><div class="typeset"><p>Hi Nathalie, <br />Can we delete from the web console now?</p></div></p> Joshua Partogi tag:visualstudio.uservoice.com,2008-02-07:Event/13399888 2013-02-15T00:08:39-08:00 2013-02-15T00:08:39-08:00 Have official and built-in support for xSpec and BDD framework <p>Joshua Partogi suggested:<br />The current opensource xSpec and BDD framework available in the market are not well integrated with Visual Studio so I think it is about time there is a built-in support for xSpec framework and BDD from .NET besides the Microsoft Unit Test framework. </p> Joshua Partogi tag:visualstudio.uservoice.com,2008-02-07:Event/13399728 2013-02-14T23:03:13-08:00 2013-02-14T23:03:13-08:00 Support application in multiple languages [updated] <p>It is crucial to have possibility to have same app in more than on language ...</p><p>mahdi said:<br /><div class="typeset"><p>I want to design app for Persian language ,unfortunately lightswitch not support Persian culture . So how can I do that by the code ? <br />Other language that is right to left is Arabic but I cant change the messages in Arabic languages that is embedded in lightswitch natively. <br />Please help how can I do that ?</p></div></p> mahdi tag:visualstudio.uservoice.com,2008-02-07:Event/13399420 2013-02-14T21:13:04-08:00 2013-02-14T21:13:04-08:00 Bring back Classic Visual Basic, an improved version of VB6 [updated] <p>The silent majority of VB6 users did not ask for changes that came with .NET We request Microsoft brings back classic Visual Basic as COM development is back with Windows 8. David Platt wrote an excellent article about why classic VB still thrives: msdn.microsoft.com/en-us/magazine/jj133828.aspx</p><p>Alejandro Hernández said:<br /><div class="typeset"><p>I&#39;ve been using VB (VB4) since bachelor. Now, I&#39;m a school teacher and I wish to teach this wonderful computer tool. Today I teach VB.Net, but I see that my students doesn&#39;t learn very quicky as they used to do with VB6. Such a shame of M$</p></div></p> Alejandro Hernández tag:visualstudio.uservoice.com,2008-02-07:Event/13399258 2013-02-14T20:16:53-08:00 2013-02-14T20:16:53-08:00 Support for immutable objects [updated] <p>Use some ideas of F# for C#. For instance, it would be very nice to have support for immutable objects, like immutable lists etc. with low costs for list changes. Also, a keyword to declare a class explicit as immutable would be helpful.</p><p>blog.nerdbank.net said:<br /><div class="typeset"><p>Have you folks noticed the release of the immutable collections? <a class="blogs.msdn.com/b/bclteam/archive/2012/12/18/preview-of-immutable-collections-released-on-nuget.aspx" rel="nofollow" target="_blank" title="Opens in new window">blogs.msdn.com/b/bclteam/archive/2012/12/18/preview-of-immutable-collections-released-on-nuget.aspx</a></p></div></p> blog.nerdbank.net tag:visualstudio.uservoice.com,2008-02-07:Event/13398498 2013-02-14T16:50:50-08:00 2013-02-14T16:50:50-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Anonymous said:<br /><div class="typeset"><p>Not having a viable setup option in the &quot;latest and greatest&quot; is nothing short of insane. So you can write applications, but there&#39;s not way to put them anywhere without spending a ton of time with a separate tool? That&#39;s crazy. It&#39;s just one more piece of evidence for me that Microsoft isn&#39;t in tune with the rest of the world. Hello?????????????</p></div></p> Anonymous tag:visualstudio.uservoice.com,2008-02-07:Event/13398272 2013-02-14T16:09:52-08:00 2013-02-14T16:09:52-08:00 Allow tests to be grouped by class, category, and namespace in Test Explorer [updated] <p>The Visual Studio team has obviously taken the time to add grouping to the new Test Explorer since we can group by test outcome and duration. However, sometimes you need to run a group of tests such as all tests in a category or namespace and this is not currently possible with Test Explorer. It would be nice if the grouping options were expanded to include at least class, category, and namespace. Then it would be possible to run all tests in a class, category, or namespace from the Test Explorer.</p><p>Anonymous said:<br /><div class="typeset"><p>Please add some sort of &quot;immediate&quot; display so that I can see what test is running?</p></div></p> Anonymous tag:visualstudio.uservoice.com,2008-02-07:Event/13398019 2013-02-14T15:30:40-08:00 2013-02-14T15:30:40-08:00 Allow for updating project templates on existing projects in TFS [updated] <p>To keep up with improving processes, there needs to be a migration path for existing templates to be upgraded to new templates. Some information in work items may be lost when mapping these to new work item types of the new templates, but this may well worth the benefits of moving to a newer process. Creating a new team project is not always feasible, especially if the source code versioning needs to be in place.</p><p>Jonathon Stevens said:<br /><div class="typeset"><p>i&#39;m confused as to why this still is here, this already happens in 2012?</p></div></p> Jonathon Stevens tag:visualstudio.uservoice.com,2008-02-07:Event/13397903 2013-02-14T15:18:04-08:00 2013-02-14T15:18:04-08:00 VS11. Bring back the old &quot;Pending Changes&quot; window [updated] <p>The new one is very confusing!!! I think the old one was almost perfect so why did you change it??? I mean, you can add new options but why did you change the philosophy? The most important problems I see with the new one: - No way to have that window independent so it can be accessed easily and fast - Difficult to see at first sight the files changed! (of course, the new “no color” interface is part of the problem...) - Difficult to exclude changes! (in the old one it was so easy by clicking the checkbox...) </p><p>Jonathon Stevens said:<br /><div class="typeset"><p>This is a classic case of, new is scary. There is a new mindset you need to work with ALL the new TFS improvements, all of which make things easier to use and flow, once you are used to them.</p></div></p> Jonathon Stevens tag:visualstudio.uservoice.com,2008-02-07:Event/13397883 2013-02-14T15:16:01-08:00 2013-02-14T15:16:01-08:00 Customize Team Foundation Service Process Template <p>Jonathon Stevens suggested:<br />In Team Foundation Service, allow the ability to change the current process template a created project is using as well as the ability to upload your own process templates to create new projecsts with.</p> Jonathon Stevens tag:visualstudio.uservoice.com,2008-02-07:Event/13397836 2013-02-14T15:10:51-08:00 2013-02-14T15:10:51-08:00 allow process editor to make changes to tfspreview [updated] <p>The tfspreview.com hosted TFS solution is great, but we cannot save changes made via the process editor. So we are stuck with the default states and transitions for workitem types.</p><p>Jonathon Stevens said:<br /><div class="typeset"><p>We also can&#39;t move to Team Foundation Service until you can modify the process template.</p></div></p> Jonathon Stevens tag:visualstudio.uservoice.com,2008-02-07:Event/13397656 2013-02-14T14:48:43-08:00 2013-02-14T14:48:43-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Paulo Kunzel said:<br /><div class="typeset"><p>For the price of a so called tool for professional developers, missing something like that is ridiculous.</p></div></p> Paulo Kunzel tag:visualstudio.uservoice.com,2008-02-07:Event/13395685 2013-02-14T11:58:56-08:00 2013-02-14T11:58:56-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>jay hammett said:<br /><div class="typeset"><p>Costing a week or more of time screwing around with WiX. We already had a setup project for deployment...MS this is a bad move. I agree with others who have wondered aloud here if the people who pushed this also happen to have stock in a very over priced third party.</p></div></p> jay hammett tag:visualstudio.uservoice.com,2008-02-07:Event/13394723 2013-02-14T10:17:08-08:00 2013-02-14T10:17:08-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Dave said:<br /><div class="typeset"><p>MS - you&#39;ve ignored to give us a commodity back even in a service pack! What good are all those &#39;great&#39; features you are adding without letting us deploy them on your own operating systems?! You should have the best idea how to do it, not 3rd party. It&#39;s like giving us fully equipped Ferrari but without keys. Sure it&#39;s still great and shiny, we can still use it - say push it on the freeway (read deploy on Azure), but we need those keys to drive! Seriously - if you ignore us now, we will ignore you in near future.</p></div></p> Dave tag:visualstudio.uservoice.com,2008-02-07:Event/13394224 2013-02-14T09:21:06-08:00 2013-02-14T09:21:06-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Bradley Mountford said:<br /><div class="typeset"><p>Well, that kills VS2012 for my team. Nice going, Microsoft.</p></div></p> Bradley Mountford tag:visualstudio.uservoice.com,2008-02-07:Event/13393508 2013-02-14T08:44:40-08:00 2013-02-14T08:44:40-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Anonymous said:<br /><div class="typeset"><p>I&#39;ve been using 2012 for months now and haven&#39;t been able to completely successfully deploy a single application. InstallShite Express isn&#39;t worth disk space, the decision was idiotic. I am seriously considering moving away from VS altogether, it&#39;s buggy, time consuming and difficult to use. I&#39;ve just about had enough of it.</p></div></p> Anonymous tag:visualstudio.uservoice.com,2008-02-07:Event/13392852 2013-02-14T07:30:51-08:00 2013-02-14T07:30:51-08:00 VS11. Bring back the old &quot;Pending Changes&quot; window [updated] <p>The new one is very confusing!!! I think the old one was almost perfect so why did you change it??? I mean, you can add new options but why did you change the philosophy? The most important problems I see with the new one: - No way to have that window independent so it can be accessed easily and fast - Difficult to see at first sight the files changed! (of course, the new “no color” interface is part of the problem...) - Difficult to exclude changes! (in the old one it was so easy by clicking the checkbox...) </p><p>Alvin Manabat said:<br /><div class="typeset"><p>The VS2010 &quot;Pending Changes&quot; window is much more usable than VS2012. Please bring that old functionality back.</p></div></p> Alvin Manabat tag:visualstudio.uservoice.com,2008-02-07:Event/13391633 2013-02-14T04:17:44-08:00 2013-02-14T04:17:44-08:00 create a way to easily migrate an existing project to git Anonymous tag:visualstudio.uservoice.com,2008-02-07:Event/13391627 2013-02-14T04:16:30-08:00 2013-02-14T04:16:30-08:00 Expand description window for Product Backlog Items <p>frodeh79 suggested:<br />When using the Scrum 2.0 process template, Product Backlog Items are used to represent User Stories. The Description area is used to document the User Story. Customer collaboration is a core agile value. The description area is currently not suited as a sharing platform between PO&#39;s, Scrum Team and other stakeholders, the area is just too small. It would be great if the description area could be expanded, at least in the web access view. </p> frodeh79 tag:visualstudio.uservoice.com,2008-02-07:Event/13391401 2013-02-14T03:28:20-08:00 2013-02-14T03:28:20-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Richard Dean Wickens said:<br /><div class="typeset"><p>What a dumb move, who ever made that decision should be dragged out into the street and repeatedly pelted with VS 2012 dvd&#39;s until they DIE! Basically I can&#39;t migrate a good 90% of my programs to 2012 if I can&#39;t build an install for them.</p> <p>Does the person who made this decision own shares in Flexera or something, because this definitely smells of someone making a decision for their own best interest and no one elses.</p></div></p> Richard Dean Wickens tag:visualstudio.uservoice.com,2008-02-07:Event/13391056 2013-02-14T02:06:17-08:00 2013-02-14T02:06:17-08:00 Add HttpClient support in Portable Class Libraries (including Windows Phone 8) [updated] <p>Yashavantha said:<br /><div class="typeset"><p>Yes, Please</p></div></p> Yashavantha tag:visualstudio.uservoice.com,2008-02-07:Event/13390803 2013-02-14T01:03:35-08:00 2013-02-14T01:03:35-08:00 Provide an option to create team project from web access <p>Anonymous suggested:<br />As in TFS 2012 administration activities are moved to web access, it would really help people to use one console to create and manage the team projects and its permissions.</p> Anonymous tag:visualstudio.uservoice.com,2008-02-07:Event/13389299 2013-02-13T17:40:48-08:00 2013-02-13T17:40:48-08:00 rename project in TFS [updated] <p>Rename existing project in TFS</p><p>JP said:<br /><div class="typeset"><p>Where do I delete my projects by Team site? I&#39;m not finding the option. If this option could make it easier on the main site manager.</p></div></p> JP tag:visualstudio.uservoice.com,2008-02-07:Event/13389275 2013-02-13T17:33:39-08:00 2013-02-13T17:33:39-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Mark Ward said:<br /><div class="typeset"><p>Let me add my two cents&#39; worth to this complaint stream!</p> <p>The BASIC Setup and Deployment project worked for EVERYTHING we have developed over the past MANY YEARS.</p> <p>Is it REALLY that hard to keep it in VS2012 (and onward)?</p> <p>I&#39;ve used InstallSheild (full product) in the past, and while it&#39;s VERY POWERFUL, it is an entirely separate product, that requires a GREAT DEAL of effort to make it do even the most SIMPLE of tasks.</p> <p>Perhaps I&#39;m the only one, but (to me) VS2012 looks like Windows 3.1 [flat, boring, unexciting] - just like InstallShield LE (a &quot;perfect&quot; match)!</p> <p>Seriously, Microsoft, is it REALLY that much work to keep the Setup and Deployment project type in VS2012? I mean, CLEARLY, you&#39;re not ENHANCING IT, so what&#39;s the problem with just keeping it alive?</p> <p>SO, for the foreseeable future, VS2010 is IT (we go NO FURTHER)... Likewise Windows 8 will probably NOT be loaded on any user desktops until Windows 7 goes END OF LIFE (heck, we still have happy XP users who are fighting going to Windows 7)!</p></div></p> Mark Ward tag:visualstudio.uservoice.com,2008-02-07:Event/13389091 2013-02-13T16:34:13-08:00 2013-02-13T16:34:13-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Artur Gomes said:<br /><div class="typeset"><p>I completely agree...</p></div></p> Artur Gomes tag:visualstudio.uservoice.com,2008-02-07:Event/13388940 2013-02-13T15:55:06-08:00 2013-02-13T15:55:06-08:00 External GIT-Server, but use TFS Work Items [updated] <p>The new native GIT support is great, but I am missing some &quot;mixed&quot; possibilities: We use a inhouse GIT server for VS, but TFS for work item tracking and with the new GIT source control provider I can not open my TFS work items anymore as it closes the GIT solution as soon as I connect to TFS.</p><p>David Gardiner said:<br /><div class="typeset"><p>+3 from me. We have TFS work items and some developers are using git-tfs for local development. Having to have two instances of Visual Studio running is a pain.</p></div></p> David Gardiner tag:visualstudio.uservoice.com,2008-02-07:Event/13388664 2013-02-13T15:00:35-08:00 2013-02-13T15:00:35-08:00 Add Simultaneous Multi-Caret editing to Visual Studio <p>Ala Shiban suggested:<br />Simultaneously edit in more than one location in the editor. If you&#39;ve ever ran into a case where you wanted to quickly change variable names or multiple loop conditions - you should be able to set more than one caret on screen and simultaneously edit/type/move all of them together An extension that does this can be found on the gallery: visualstudiogallery.msdn.microsoft.com/2beb9705-b568-45d1-8550-751e181e3aef</p> Ala Shiban tag:visualstudio.uservoice.com,2008-02-07:Event/13388648 2013-02-13T14:57:24-08:00 2013-02-13T14:57:24-08:00 Support elastic tab stops [updated] <p>Support elastic tab stops! Just look at the picture on this web site: nickgravgaard.com/elastictabstops/ P.S. we should be able to make the choice between spaces/tabs/elastic tabs on a per-solution (or per-project) basis.</p><p>Ian Prest said:<br /><div class="typeset"><p>Awesome idea! Probably hard to implement, but really cool.</p> <p>The tab-size per project is a no-brainer, though, and should be a lot easier to implement.</p></div></p> Ian Prest tag:visualstudio.uservoice.com,2008-02-07:Event/13388643 2013-02-13T14:56:31-08:00 2013-02-13T14:56:31-08:00 Bring back the basic setup and deployment project type Visual Studio Installer. [updated] <p>You really need to bring back the basic Setup and Deployment project name Visual Studio Installer. It was a clean, simple, and effective installer for home grown applications that were to be deployed internally. I downloaded and used InstallShield LE and it&#39;s too complicated and overblown to build simple effective install/uninstall capabilities. Why did you remove it to begin with? We have to support desktop applications for the foreseeable future. </p><p>Min Pan said:<br /><div class="typeset"><p>Dear Microsoft Team, <br />We need the setup and deployment project back! Have been using it for years without any headache. Very glad to hop on VS 2012 only to realize at the end of development that InstallShield LE is a drag, at least for simple internal deployment. Missing this basic component has pushed many of us trying to find alternatives over the internet, which will not bode well for Microsoft, from a strategic point of view… </p></div></p> Min Pan tag:visualstudio.uservoice.com,2008-02-07:Event/13388313 2013-02-13T14:01:51-08:00 2013-02-13T14:01:51-08:00 Create a &quot;miscellaneous&quot; project type <p>Joe Parker suggested:<br />I would like the ability to create a &quot;miscellaneous&quot; project that simply lets me add arbitrary files to it for ease of opening them up in the IDE. The project would not do any kind of building or packaging; it would only be for convenience in managing miscellaneous files. In my particular case, I have SQL scripts that I do not want to be part of a formal VS Database project. All I want is a convenient way to open them up in the IDE for editing. Right now I am using a formal Database project for those files, but I have to fight it to get it to not do anything. And when that same project is open in multiple solutions, I get errors about the database model file being locked, which is annoying because I don&#39;t even care about that. It would be nice to have a project type designed simply to hold a collection of files, and nothing else.</p> Joe Parker tag:visualstudio.uservoice.com,2008-02-07:Event/13387953 2013-02-13T13:03:05-08:00 2013-02-13T13:03:05-08:00 Provide Better DirectX support in WPF [updated] <p>These DirectX support classes are new in WinRT / Metro. Please provide them in WPF. SurfaceImageSource enables full composition of DirectX content into a XAML app. This allows drawing DirectX content into the XAML visual tree, useful for complex image effects, data visualization, and other immediate-mode drawing scenarios. VirtualSurfaceImageSource is used for large-scale virtualized content. This is targeted toward apps that require panning and zooming of large content, like maps and document viewers. SwapChainBackgroundPanel targets full-screen, DirectX-focused scenarios. This is great for games and other low-latency, full-screen DirectX apps with a XAML overlay.</p><p>Denis said:<br /><div class="typeset"><p>Yes, please, make a normal way to use native DirectX C++ in WPF applications. It would be very helpful writing level editor for games, for example.</p></div></p> Denis tag:visualstudio.uservoice.com,2008-02-07:Event/13387565 2013-02-13T12:16:06-08:00 2013-02-13T12:16:06-08:00 encapsulate multiple class variables <p>Chris Johnson suggested:<br />I use the Refactor -&gt; &quot;Encapsulate Field&quot; tool a lot and it would be great if after I type multiple new variables inside a class, I can run the tool in a batch/loop where it&#39;ll search the highlighted code, and refactor each variable it finds until it reaches the end of the selected code. Along with giving the user the option to set the preferences for the tool on the first variable and then use those same preferences for each variable it comes across in the loop. Lastly, it&#39;ll put all the new property declarations in the same area for easy copy &amp; paste.</p> Chris Johnson tag:visualstudio.uservoice.com,2008-02-07:Event/13387409 2013-02-13T11:54:20-08:00 2013-02-13T11:54:20-08:00 As a trainer, administrator and ALM professional it would be great to have one integrated utility to setup a TFS instance quickly <p>Jesse Houwing suggested:<br />The ALM Rangers have the TfsTeamTool Quick Response Sample, a tool from Tarun which adds some additional features, the Scrum Robot which Richard Hundhausen uses with a collection of batch files and scripts for the PSD.NET training course. And my personal additions for setting Team and Personal profile pictures. It would be valuable to consolidate these into a single well organized set of commands that can be used to quickly setup a demo or trainign environment.</p> Jesse Houwing tag:visualstudio.uservoice.com,2008-02-07:Event/13386985 2013-02-13T10:59:45-08:00 2013-02-13T10:59:45-08:00 Sorting &quot;Assigned To&quot; Field <p>Michael Tyomkin suggested:<br />It would be great if &quot;Assigned To&quot; field was sorted not only alphabetically but also by whether the person is on the team or just has access to the project (ex. a member of another team in my project). I have a few &quot;Davids&quot; and &quot;Michaels&quot; in my larger Org, but only 1 of each on my TFS team.</p> Michael Tyomkin tag:visualstudio.uservoice.com,2008-02-07:Event/13386763 2013-02-13T10:34:24-08:00 2013-02-13T10:34:24-08:00 Easy way delete a task or work item in Team Foundation Server [updated] <p>It is common to make a few mistakes, duplicates etc when entering a bunch of new work items or tasks. There is no easy way to delete the bad ones and try again. I know it is possible to to do this from the comamnd line, but it is a pain and defeats the purpose of having a GUI. The end result is that poor items get left in the project because it is a pain in the *** to remove them and start over.</p><p>Anonymous said:<br /><div class="typeset"><p>please fix this.... we can&#39;t use tfs anymore becuase we can&#39;t delete items. </p></div></p> Anonymous tag:visualstudio.uservoice.com,2008-02-07:Event/13385835 2013-02-13T08:39:36-08:00 2013-02-13T08:39:36-08:00 Master ALM Treasure Map [is now completed] <p>Is there a master document (e.g. Word,
gipoco.com is neither affiliated with the authors of this page nor responsible for its contents. This is a safe-cache copy of the original web site.