Visual Studio

Welcome to the Visual Studio UserVoice site! Let us know what you would like to see in future versions of the Visual Studio suite of products. This site is for suggestions and ideas. If you need to file a bug, visit the Visual Studio Connect site: https://connect.microsoft.com/visualstudio.

We would also like to invite you to check out the Announcements section we have added to this site, where we will be posting special opportunities for you to participate in.

Interacting with SharePoint from javascript in HTML Client requires loading the SP CSOM scripts, referring to the AppWebUrl and HostWebUrl, and for HostWeb Calls - the cross-site request executor is needed.

All these operations are happening in msls.js and are nicely built into the msls.sharepoint object, however that object is contained in an anonymous self-executing function and it is not exposed via msls.expose().

Therefore the msls.sharepoint object cannot be used in custom code at runtime without altering msls.js

If it were exposed, then we wouldn't have to duplicate the above requirements when do scenarios such as:

Create or alter lists; Check for existence of an item; upload documents; check group membership; query items in order to... let's say, populate a choice list; anything else that requires a call to sharepoint.

CBA is THE RAD tool for sharepoint apps yet many LS devs haven't yet fully dug into the SP REST API. It only makes sense to expose the msls.sharepoint REST executor so we don't have to deal with the requirements - we can just post a request using the familiar promise operation.

Another benefit is, if the object were exposed, we could extend it. Devs could build all sorts of useful new reusable methods and append them to the msls.sharepoint object while avoiding any changes to msls.js.

By the way, this goes for any of the msls objects and methods. For example, anyone want to create controls in the msls.ui.controls namespace? Can't - it's not exposed.

Thanks for listening \ Voting.

Interacting with SharePoint from javascript in HTML Client requires loading the SP CSOM scripts, referring to the AppWebUrl and HostWebUrl, and for HostWeb Calls - the cross-site request executor is needed.

All these operations are happening in msls.js and are nicely built into the msls.sharepoint object, however that object is contained in an anonymous self-executing function and it is not exposed via msls.expose().

Therefore the msls.sharepoint object cannot be used in custom code at runtime without altering msls.js

I do not know why,
When I want to show the detailed, but could not see anything.
View console found.
"Failed to load resource: the server responded with a status of 401 (Unauthorized)"
What causes it?
Free limit account yet?

I find it a waste of time to have to open my Build Collection, select any build, and then using context menu select "View Builds" just to open the Build Explorer Window. It would be less time consuming to be able to use a control key combination, or add a button to my menus, that would allow me to go straight to this window with the default options of viewing all builds completed today. As the SCM administrator, one of my tasks is identifying why builds break and letting the appropriate development tema know.

There should be a popup message notification in Visual Studio 2012, if we are connected to TFS and if any team members does code check in, so that other developers can get change set details immediately.

Add Path property to VS2013 Installer Projects Extension.
This would allow developer to control the location of their source code = their msi deployment project.
As of May 09 2014, developer launches new project, deployment install.... VS2013 R2 w/ VS Installer Projects Extension creates "Setup1" folder under the subject's app main project folder.... would be best if that location (path) could optionally be adjusted by developer.

When using the Fakes Framework to generate Stubs, the Fakes Framework will change the method name of a method such as Save(Student student) to SaveStudent. This really messes with the clarity of the code and Unit Tests. Therefore, in a manner similar to most Mocking Frameworks, the same exact method names as are available in the interfaces and concrete classes should be used rather than generating brand new method names to be used in the Stubs.

Currently, the Fakes Framework requires compile time assembly generation each time. However, this significantly slows down build time and greatly inhibits the refactoring process. Instead, Fakes should use a model similar to mocking frameworks such as Moq or RhinoMocks in the ability to use dynamic proxy classes when the Unit Tests are run. This significantly reduces build time and is not as obtrusive a process as generating Fakes assemblies that require a complete re-build of the project as part of the refactoring process.

Enhance TFS command line tool to output query of all occurrences of an identity's usage. This could be narrowed to server or collection, etc. So results would include group memberships, checkins, workitems, everything that can be id'd with a Team Foundation user ID.

Integrate support for the GNU toolchain into Visual Studio. It would be great if VS could load those c++ projects natively. So in essence VS could read and understand Automake, m4, libtool etc. Even better, let VS convert such projects into VS format.

Add setting in Options to have the 'Keep test execution engine running' setting default disabled. I have build problems when the test execution engine keeps running after performing a unit test. Regularly, I forget to disable this option when I start Visual Studio, so I need to restart Visual Studio.

It seems that WPF is not in the Microsoft plans for a near future. And lots of developers still use this as a rich platform for desktop.
Please make WPF oepn source, following the success of MVC and EF.

Would be great if we can generate report on Measure reportable type of field due to is a crucial field to check the health of an Scrum team.

This is related to the following issue:

TF208067: The following filter will not be added to the PivotTable and PivotChart reports. The filter uses the Completed Work field, which is reportable as a measure. Click Finish to create the reports without the filter, click Back to specify another query, or click Help for more information.
[Completed Work] >= 1

Here is my query:

Team Project =
@Project
And Iteration Path
Under Sprint to 06-12
And Completed Work
>= 1
And Work Item Type
= Task
Or Work Item Type
= Bug

My query returns the correct result but the excel report generates incorrect result on total number of Completed Work.

I was advised that the Measure reportable type of field cannot be add in the PivotTable and PivotChart in Excel report, the Completed Work field is Measure reportable by default, so I will receive that error when try create your query as report in Excel, that’s an expect result.

Would be great if we can generate report on Measure reportable type of field due to is a crucial field to check the health of an Scrum team.

This is related to the following issue:

TF208067: The following filter will not be added to the PivotTable and PivotChart reports. The filter uses the Completed Work field, which is reportable as a measure. Click Finish to create the reports without the filter, click Back to specify another query, or click Help for more information.
[Completed Work] >= 1

You do not have API exposed. Gomez and Keynote, which are competitors for appInsight, have an api that can hook into SCOM. If you want to make VSOnline useful, please allow your customers to send the data to other sources.