I want to look at (a label name for example in) the properties box (shown by clicking the element in the interface window) and scroll through my code until I find what I'm looking for. The problem is that as soon as I click the code window, properties goes blank.
Is it possible to change this behavior?
It's annoying to copy and paste or (gasp) remember what I was just looking at.
the properties window is context-sensitive, so it shows properties for whatever it is you're looking at - in your case, code. now it just happens that code has no properties to show, which is why its blank.
I wouldn't want to change it - next thing you know, you'd be clicking on something and not seeing the properties for it! That would be bad.
Related
This is a simple issue, and I hope someone can help
For reasons I don't think I need to explain, my XAML thinks it has some errors in it in the Visual Studio code editor (which shows as wavy blue underlines across most of my XAML).
Does anyone know how to turn this underlining off in Visual Studio 2012 ?
It's incredibly annoying, and makes my XAML hard to read
Thanks
I would suggest setting the editor for .xaml-files manually.
Go into
Tools->Options->Text Editor->File Extension
Write xaml in the Extension field and choose XML (Text) Editor from the Editor drop down and then click Add.
Your XAML files should now open as ordinary XML files, without error underlining.
You will probably loose a lot of the nice to have features of the XAML editor, but as far as I know (I've struggled a bit with this myself) it is the only way.
Found this on MSDN. There is a specific setting to disable this.
Open the Options dialog by selecting Tools > Options, and then select
Text Editor > XAML > Miscellaneous.
Uncheck the Show errors detected
by the XAML designer check box.
Article from MSDN
It is possible to hide the SquiggleShape by making the surrounding adornment layer hidden or collapsed using the Snoop tool.
To achieve this, the Snoop crosshair tool has to be dragged on the editor window with shift and ctrl keys pressed (keep them pressed a while when releasing mouse button). You should end on some Canvas (with the editor window highlighted), and below there is some ViewStack. Inside, there are some AdornmentLayer, one of which contains multiple SquiggleShape. In the properties section on the right side of the Snoop window, scroll to the Visibility row and select the value Hidden or Collapsed. Now, the squiggle lines are not visible any more.
This involves some manual work, but as long as the file stays open, the squiggle lines are hidden. In principle, it should be possible to write an extension which hides the lines automatically. However, at the moment I don't find the time to do this...
The only decent fix for this silly bug that I can find is right click on the xaml and click open with. Select source code editor (without with encoding). Not a great fix when you consider it gets rid of important errors. But it should help you read it better for the most part.
Another Option for this is to change the color of the line under: Tools > Options > Environment > Fonts and Colors. Change it to the same as the background.
It will turn it off in all other editors also though.
I am curious about an issue in Coded UI Testing. For example I created a button named Button1. I did assertions and everything is fine. Then I changed this button's name to Button2. Now, do I have to write my assertions again or is Coded UI Test can suit in every different name change. Notice that I am not doing any input or parameter changes, I am just changing user interface. Thanks for your replies.
You should be able to change the test code easily to cope with a name change like that. Open the UI Map file in the UI Map editor; ie double-click on the uimap.uitest file in solution explorer. In the left hand pane expand the method and select the action that clicks the button. That should open the relevant control in the right hand pane. Alternatively just find the control for the button in the right pane. View the properties of the button and click on the ellipsis of the "(collection)" value of SearchProperties or the FilterProperties. One of the items shown should be the old name of the button, just rename it there.
I am trying to add a shortcut to the exectuable in the user's start menu.
There are many answer on StackOverflow that detail how to do this.
However, the all say something along the lines of 'Right click in the right-hand pane to...'
So I understand you all have an interface that looks something like:
I don't have the panel on the extredme right - entitled 'Name' containing the Primary Output.
I have gone through every menu option I can find to enable this pane, but can't find it.
Anyone know how to show this window?
I am wondering wether or not the splitter has been dragged all of the way to the right. Try collapsing all of your side menus like the solution / property / toolbox etc.. to make sure that the File System editor is filling the entire window then look if you can see a splitter to the right. I have not found any way to delete that panel yet. You can also try right clicking on the File system Tab and tell it to float then make it go full screen to see if the splitter is visible then.
I had the same problem, tried to find another splitter but couldn't, got the 2nd detail pane by opening Visual Studio 2010 using the 'Run as administrator' command.
I'm not sure if this is right, but I can't view the "code behind" in VB6. Everytime I click the "view code" for an object (for example a button), the code does not display.
Can you help me with this or any workaround for this? I need to do a breakpoint on this.
I ran into the same issue. Could not view the code or the designer.
Seems that VB6 lost track of where things should be displayed, whether offscreen or not I could not tell. Kept clicking View Code and View Object, and neither worked.
Found the solution:
Attempt to open the code or designer that doesn't show up. (It will get opened, just won't show)
Select Window from the menu, then select Cascade.
You should then see the code/designer show up on the screen. No re-install or remove/add needed.
You may need to do this each time, even after saving the .vbp (project) file, upon re-opening VB6 the files once again are not showing for me, but Cascade makes them visible again. (Anyone have any ideas on how to make this more permanent?)
Enjoy!
You may remove the form which is not showing the code in the project explorer window and add it again by right clicking on the project explorer window then select Add -> Form -> (instead of selecting in "New" tab navigate on the "Existing" tab then choose the form you have just remove and try viewing its code again). It will work 100% :D
Double click your controls and the source code will be shown.
Go to this link.
vb6 tutor
I'm trying to customize some TFS work items via the VS2008 xml editor, but every time I open a work item xml file it jumps to the graphical designer. All that gives me is a "View XML" button that doesn't let you edit the xml directly.
I don't have TFS but I know in regular VS there is an Open With... option in most items' contextual menu that even let you change the default editor. Very useful when you are tired of the Designer opening instead of the Code file on Windows forms.
Ah, looks like you have to go to File->Open and click the down arrow next to the Open button to "Open With" the xml editor. If someone wants to copy and paste this, free accepted answer :P
As per Coincoin's answer, this feature is also great for setting the default editor for ASPX. If you want to go to the Code Editor most often, then this is a default you'd want to change.
Reading this - I think perhaps you don't realize - that there is no need to edit the XML - in fact it is very difficult to do so. The graphical designer will actually let you change the Work Item type, adding new fields, changing workflow, rules etc.
The only reason to change the XML is if there's a bug in the Process Editor (the tool that gives the graphic designer). I have done extensive modifications of Work Item types and only had one instance where I had to change the XML.