I don't seem to have the option "HideMemberIf" which is used for creating ragged hierarchies (on all videoes and websites I have seen). I only have the option "Display Folder" under the advanced field. How do I get the HideMemberIf field?
enter image description here
Related
Visual Studio 2019 Pro, v. 16.11.13.
A Solution with about 100 projects. All projects are included in the build process. Solution was opened about a half an hour ago, and was just fully rebuilt.
I'm clicking on some const field and choose "Find All References" - nothing was found, except the "Symbols without references". Then I'm trying to find this field through "Find in Files", and it found me a reference to this field inside some Razor page. Checked - there are no broken references. The project, that references to this field, has reference to the project, that contains this field.
But! After opening the Razor page with this field, now it can find this field through "Find All References".
What? Why? For what reason?
I am using Visual Studio 2017.
I can expand and collapse in .cs files using command as follows:
Expand CTRL+M+L
Collapse CTRL+M+O
But same is not working in .cshtml file? Is there any workaround?
Ctrl+M+A collapses all, Ctrl+M+X expands all in my installation. You can see them by opening Tools > Options..., select Keyboard under Environment. In the Show commands containing, find Edit.CollapseAllOutlining (you can search too) and Edit.ExpandAllOutlining. You should be able to see the existing binding or add your own (make sure to select Text Editor or Global).
From what I could determine, Visual Studio doesn't support expanding and collapsing for this file type.
There is a sort of workaround, although it has its limitations. You can manually select regions in a given file that you'd like to hide and press Ctrl+MCtrl+H (also found in the Edit->Outlining menu) to hide them. Visual Studio will "remember" that you want these specific regions to be hideable, and you can now show and hide these sections with the outlining commands (for example Ctrl+MCtrl+A will hide all sections, and Ctrl+MCtrl+X will show all sections, depending on your keybindings).
This isn't a perfect solution by any means, because you need to set up the regions manually. But it might come in handy in some cases.
Here's an example of a .cshtml file after I set up the regions:
...and after pressing Ctrl+M+L once:
I am trying to figure out how to modify the work items permissions on a specific TFS project to inaccessible?
I want to make the work items 'invisible' to all users.
The MSDN documentation is a little unclear (at least for a newbie):
http://msdn.microsoft.com/en-us/library/ms252587.aspx
it mentions TFSSecurity could be used from command line and I think i need to deny WORK_ITEM_READ for that project - could someone provide the syntax for that?
Thanks!!!
You can do it with TFSSecurity. But unless you enjoy command line pain, just use Team Explorer (via Visual Studio).
Right click on a project in Team Explorer and select "Team Project Settings" then select "Areas and Iterations".
In the resulting dialog make sure that the root Area (called "Area") is selected then select the "Security" button in the bottom of the dialog box (next to close).
That will launch the security options for the work items under that Area. From there you can uncheck "View work items in this node" for everyone in the list.
However you will be unable to remove Collection admin's rights to view the work items. You may be able to do that via TFSSecurity.exe but it would be abnormal to do so.
I have 3 people working on 1 Team project in TFS. I want to see all the users' work from the date when this Team project was branched until the day the last user checked in his work. It's required so I know how many files to transfer to another server.
Does anyone know if there is a way? I did "view history" and it didn't really give me what I wanted.
Get yourself a copy (free) of the TFS Power Tools. It contains a great feature called Find In Source Control. This allows you to search for check-ins based on a number of criteria, including a range of dates, or a begin and end changeset number, and more.
Randy Minder's answer should meet your needs as stated in the question. But, if you want to see the work represented in another way, you can compare your work to the server path from which it was branched.
From the View menu, choose Team Explorer. Browse to the project your project and double-click on the "Source Control" node. This opens your "Source Control Explorer".
In Source Code Explorer, right-click on on the folder where you've been working. Choose "Compare" from the menu. This will open a dialog that compares two server locations for differences. By default, the folder you've just clicked on will be the Target Path of the comparison.
In the dialog, click on the Source Path Browse button and choose "Source Path". Another dialog will appear, asking you to choose a path on the server.
Browse to and choose the server path from which you branched.
Visual Studio will now give you a comparison (recursive through folders) of the two paths, showing which files have changed and easily letting you inspect differences and histories of those files.
If the Source Path hasn't changed since you branched, and you've checked everything into the Target Path, the "Folder Difference" pane should represent the work you've done since you branched.
In VSTS 2010 – in MS Test Runner
A defect can be logged against a work item called “BUG” by default.
This bug will have all the details relevant to the test that is run like the information in the following tabs in workitem bug – details tab, System info tab , Test Cases tab, etc .,
Instead of logging defects in workitem “BUG” is it possible to log defects to any other custom workitem but still manage to hold all these details tab , system info tab , test cases tab, etc., into the custom WI.
Please refer the attachment .
You need to put your custom work item type into the Microsoft.BugCategory category. Take a look at the command line tool witadmin in %ProgramFiles%\Microsoft Visual Studio 10.0\Common7\IDE
The following blog post might help you:
VS2010 Work item categories
If you want all the controls as well (like repro steps control), then you need to make sure the appropriate fields and form controls are copied over into the work item from the Microsoft work item definitions.