Is there only Horizontal Split as default and not Vertical Split? Again or my eyes are going bad? It was an issue in VS2008 and VS2010 when it was per-file basis so nothing has changed?
Yep there is currently no way of defaulting to a vertical split for the XAML designer in VS2012.
Like you mentioned the only way at this point is doing it per-file basis as these settings are saved together in your .suo file.
This applies to VS08 and VS10 or VS12...
If you do want to let microsoft know that you would like this to be a feature you can send them a request here
Here is the original thread about this issue.
Its funny though that their HTML designer does allow defaulting to vertical split..
Related
My Alexandria Delphi IDE has lost its color control for Standard Components.
I cannot set the Font color at design time for components like TLabel, but it's correctly applied at run time.
Non-standard components i.e. JvLabel seem to work at design time and run time.
Parent Font is False.
Have I screwed a setting somewhere?
From my point of view this is a new bug in the Designer of Delphi 11.
In Delphi 10.4.2 the color display of TLabel.Font.Color still worked correctly in the Designer.
I recommend creating an RSP in Embarcadero's Quality Central for this bug.
Update 19-Jan-23:
This is an already known problem of Delphi 11.X.
You can uncheck "Tools->Options->User Interface->Form Designer->mimic the system style" option as a workaround.
I want to be able to use things like the Solution Explorer window or the Properties window from Visual Studio in my Windows Forms application. I am not sure what the term for it is so I cannot look it up.
Have you tried using a normal panel? You might want to code all the contents of the solution explorer and the properties panel. The panel can be docked from its properties. Then, for example, if autosize is disabled, you write
If ...... Then
_something_.Autosize = false
End If
But that's a TON of code!
I don't think you can reproduce the solution explorer dynamically nor the properties panel. Besides, do you need to change all properties of an object at once? It looks like you are trying to remake visual basic dynamically. Well, that can't happen. Not with the current versions of vb.net, at least.
You should try involving things with panel that appears on your screen with all the settings in it, but like TGamer, there is a lot of code to do. But start with showing and hiding the panel to start with. Maybe try importing the settings through a VS file stored somewhere in your directory.
I'm looking for a way to inspect running XAML in a Windows 8 store app. Essentially, I want firebug / chrome inspector style functionality where I can look at the XAML source generated at runtime, to debug simple layout and style issues.
I've tried Snoop, Pistachio and WPF Inspector but none work for Windows Store apps. The only one I can find which seems to work for Store apps is XAML Spy, which is €90. I can't justify that cost.
Is there any other way to inspect running XAML?
WinRT XAML Toolkit now has an actual visual - visual tree debugger.
Get it from NuGet: nuget.org/packages/winrtxamltoolkit.Debugging then call WinRTXamlToolkit.Debugging.DC.ShowVisualTree() to display the debugger tool inside of your app. It's the third option so now you can use
the WinRTXAMLToolkit.Debugging.VisualTreeDebugger class - that enables you to debug the tree in your Visual Studio
XAML Spy - which is a great commercial visual tree debugger that runs in a separate window
and now this visual tree debugger in the WinRT XAML Toolkit that works inside of your app.
The VisualTreeDebugger class from WinRT XAML Toolkit is what you could use if you want a free tool. It doesn't do as much as XAML Spy, but you get what you pay for. I thought of adding more features to it like actual visualization of what you debug, but the work required would not justify the time investment + I didn't want to step on Koen Zwikstra's turf. I am sure he is doing a great job on that tool. Anyways - VisualTreeDebugger is enough for me, so maybe it would also be enough for you.
The way you can use it is add the class to your code, add a reference in your XAML like
xmlns:debug="WinRTXamlToolkit.Debugging"
then put a hook on a control where you would like to start debugging, like
debug:VisualTreeDebugger.BreakOnLoaded="True"
which will dump the core visual tree details as text in your debugger output window (Ctrl+W,O) and break in the code that dumped your tree where you can investigate the "path" variable, which contains the list of all visual tree elements from the debugged control to the root, so you can watch their values if what you need wasn't already dumped in the output window.
Other options include
debug:VisualTreeDebugger.BreakOnTap="True"
debug:VisualTreeDebugger.BreakOnLayoutUpdated="True"
debug:VisualTreeDebugger.BreakOnLoaded="True"
debug:VisualTreeDebugger.TraceOnTap="True"
debug:VisualTreeDebugger.TraceOnLayoutUpdated="True"
debug:VisualTreeDebugger.TraceOnLoaded="True"
Since it is source code and really a single simple class - you can easily add additional things to the code to do any custom debugging you need.
XAML Spy is what you need. You find it at http://xamlspy.com.
there is a new free tool called XAML Inspector. It's available through NuGet. Just search for "xamlinspector" or get if from the project page: www.xamlinspector.com
Greetings
Christian
After each build, Visual Studio 2012 switches from the Solution Explorer to the Code Analysis tab, usually with the yellow "No code analysis issues were detected." (Might as well say "TA DA!").
Is there an option to turn off the tab switching (keeping it on Solution Explorer)? [because I can't find it either in Solutions or Options].
Thanks!
VS 2012
The best answer I have found so far is to drag the Code Analysis view's tab away from the Solution explorer. I've docked mine below the Solution explorer and made it about 1 inch high - so I can still see what it is reporting on the rare occasions when I wish to check it, but without losing my Solution Explorer all the time.
It's still unnecessary but a lot less irritating.
Update - VS 2013
In VS 2013 you can now click the Settings option in the Code Analysis view, and disable the Show window when issues are detected option.
Right Click Project --> Properties --> Code Analysis Tab --> Uncheck Enable Code Analysis on Build.
Hope that Helps.
Just found very helpful blog post about your issue Temporarily disable the C# static code analysis for a whole VS instance.
Also I have found way to permanently disable Code Analysis for all VS 2012 instances:
You need to add Windows environment variable with name "DevDivCodeAnalysisRunType" and value "Disabled" (all without quotes). There is helpful post about Windows environment variables How To Add/Edit Environment Variables in Windows 7.
Hope that helps.
Most of the time when I code, either using Visual Studio or gVim, I like to have many open windows with code files so that I can go back and forth from one to another, either to edit or just read while editing another file.
Thus I found VS 2010's feature of "floating" code windows very helpful. However, the fact that when a code window is floating, it's "always on top" is a bit annoying, because it might hide other windows, such as the "Find Results" for example.
Is this something that is customizable? Is there a configuration value somewhere that either enables or disables the "always on top feature" of floating code windows in Visual Studio 2010?
Thanks
Well, it is not a real top-most window, it is merely on top of the Visual Studio main window. An 'owned' window. From where it competes with other windows that VS displays for the Z-order, like the Find Results window. You'd need to arrange these windows so they don't easily overlap and obscure each other. That's supported, you can dock them. Bit of a chicken-and-egg problem, isn't it?
If you have concrete ideas how to improve this then you can post them to connect.microsoft.com