How to clear the output window in Visual Studio 2022 before each run automatically - visual-studio

I have a simple .NET Core 6 application, developed via Visual Studio Community 2022.
When I press the start button in the standard toolbar, it appends the logs in the output window.
If I want to distinguish the start point of the recent run in the log's lines, I must search in the console.
There is a button in the top corner of the output window for clearing the console before the next run.
My question is, is there any setting in Visual Studio that I can set, to clear this output window automatically in each run before starting logging?

Here's my cheat-to-win workaround. It's not exactly the same as clearing the output window but it sure gets rid of the noise.
Debug.WriteLine(string.Join(Environment.NewLine, Enumerable.Repeat(string.Empty, 100)));
In the past I would use the technique shown here EnvDTE80.DTE2 to do a legitimate Clear but apparently there's no support for System.Runtime.InteropServices.Marshal.GetActiveObject in net core as mentioned here .Net Framework but not for .Net Core

Related

Web Publish Activity window is not maintained when closing and reopening Visual Studio 2022

I recently applied an update to Visual Studio Community 2022 (64-bit).
Current Version is 17.3.4
We still use Web Deploy for some legacy asp.net sites and the Web Publish Activity window is very useful for switching between dev and production environments.
After a recent Visual Studio upgrade I noticed that the Web Publish Activity window was not visible, so I reopened it via View -> Other Windows... and it appeared as expected in the lower window, as a new tab along with Output and Error List.
But after closing my project and reopening it, the Web Publish Activity window is missing again. I tested other windows like PowerShell and Bookmark Window and they ARE maintained after closing and reopening VS.
I also tried saving a new window layout with the Web Publish Activity window open and then reapplying that layout after a VS restart but that had no affect.
It is very annoying to have to go though multiple levels of the View menu to reopen this window every time I open this project.
Does anyone have any advice on how to keep this window locked/pinned?
Is Microsoft trying to "encourage" me to stop using this window?
If there is another way to quickly change between publish profiles that would be acceptable as well, but I cannot find one.
Thank you.
This may be a bug with this particular window (the fact that it doesn't stay pinned after closing Visual Studio that is).
Perhaps as a decent workaround you can at least assign a keyboard shortcut to open this window:
Go to Options → Environment → Keyboard
Filter down to "View.WebPublishAcitvity" or find it in the list
Create a keyboard shortcut of your liking by typing it in the circled red box and then click the Assign button:
After doing that, you should be able to use that shortcut to open the window much faster at least.

Visual Studio 2019: Start Page instead of Start Window

Visual Studio introduced a blocking Start Window instead of a non-blocking Start Page.
Considering how extensible Visual Studio is, is there a way to have VS2019 display a non-blocking Start Page.
The new Start Window is quite annoying, less informative, displays all projects, not just solutions, pinning is not up to previous standards, and no additional information. Most annoying is the blocking aspect.
I am thinking that there is some sort of extension or setting that Microsoft has somewhere, which can re-enable the Start Page and disable the Start Window.
Alternatively if it is not possible, is it possible to just disable the start window and have the main application appear, when the app starts or when a user closes a solution/project?
--
Another hope with this post is that Microsoft sees this request and maybe modifies their code and offers users an option at the start, much like color theme and default code set, as to whether they want app blocking or app non-blocking for the start area.
In Tools > Options > Environment > Startup > On startup, open: select "Empty environment".
Visual Studio will start without showing the modal Start Window.
Start Page on startup extension restores the traditional Start Page in VS 2019.
Start Page: Please give it back! and Make the Visual Studio 2019 start window non-modal are open issues concerning your other points.

Dock Code Windows in Visual Studio 2010

In Visual Studio, you are able to dock code windows in horizontal and vertical tab groups (something you can also do with tool windows).
However, when doing so you may end up with a lot of redundant screen space. What would be ideal would be if you could mix docking orientations for code windows. This is possible with tool windows in Visual Studio 2010. Here is an image showing the feature used for tool windows:
My question is: is it possible to get this same functionality with the code windows - i.e. being able to mix horizontal and vertical docking, like with the tool windows shown? I've heard rumours that its possible, but I've been unable to find any truth in that.
I too wish this was a naitive feature in visual studio, but there is one workaround by using the 'floating tab group' feature of visual studio
Move the visual studio main window out of the way (maybe to another monitor, or to smallest area of the monitor needed to see the tooling windows)
"Tear out" or Right Click > Float on the desired tab
Position the tab to your desire (I suggest using WinSplitRevolution, via codinghorror)
Repeat, note that you can move a tab to an existing 'floating' tab group
And voila!
There are some setbacks, some commands will pop up over the main tooling window instead of your current tab group etc. but its still pretty nice. I'm not sure if there's any changes coming in VS2012, but I haven't heard about anything related.

Visual Studio output window- what goes there and why?

Can someone please explain to me what goes to the Output window in VS? Where do the messages there come from and do they have other use other than for debbuging?
Thanks.
The Output window is a set of text panes that you can write to and read from. Visual Studio defines these built-in panes: Build, through which projects communicate messages about builds, and General, through which Visual Studio communicates messages about the integrated development environment (IDE). Projects receive a reference to the Build pane automatically through the IVsBuildableProjectCfg interface methods, and Visual Studio offers direct access to the General pane through the SVsGeneralOutputWindowPane service. In addition to the built-in panes, you can create and manage your own custom panes.
Output Window (Visual Studio SDK)
This panel shows the actual info, that is spit from your application to the console (no matter debug or run mode). Also building, rebuilding and cleaning your project is described as operations there.
Check F1 for more info ;)
By default it either shows output from the build process, or debugger output. You can use OutputDebugString to display text in the output window while debugging.
There's not much else you can do with it without using an Add-In for Visual Studio.

Visual studio does not show content of files

Picture says it all, it should currently be showing a file but as you can see its having issues drawing the content of the file.
I have unloaded all addons and restart visual studio.
If it mathers the previus project was a VS 2k8.
New Info:
If i wait a good 5min ( I have a Quad core I7 with 6gb ram, 295gtx. VS is running from a SSD).
It will load the text, but im unable to "edit", as it will have loaded some document (.cs ) but when i select the one i want to edit it not realy open that file.
It can best be described as visual studio having a 5min lag.
I had this precise bug. I would open files from the solution explorer but the editor window would either not appear, only 1-2 lines of 100+ line files would display, or the file would display but I could not scroll or otherwise edit the file. Some parts of VS were working, i.e. little tooltips would appear if I moused over the right part of the (invisible) text but I obviously couldn't do much in this state.
I have a lot of VS stuff installed so I thought it was some sort of plugin or extension that was causing things to go screwy. These installed items include:
Visual Studio 2010 10.0.30319.1
ReSharper 5.1.3000.12 (JetBrains)
DevExpress DXCore 10.1.5 (free community edition)
DX Source Outliner (reason for DXCore, from sbohlen)
Tabs Studio 2.0.6 (www.tabsstudio.com)
Productivity Power Tools 10.0.11019.3 (Microsoft)
Snippet Designer 1.3.0 (Matt Manela)
I solved it (2/18/2011) by Tools... Extension Manager... disabling the Productivity Power Tools and Snippet Designer. No idea what was going on but this fixed it for me and I was back to work. Probably something in the system drawing and/or display options.
EDIT
The issue continues. Unfortunately it is intermittent and I have not be able to reproduce it reliably. Now the suspects are the BugShooting and CaptureWiz screen capture tools. I've had the behavior show up and then disappear in and around the time of logging bugs with them.
2nd EDIT
The issue continually continues. I have not yet been able to determine the cause but usually quitting VS and restarting resolves the issue(s). Other parts of the behavior includes the menu options (File, Edit, View, etc.) not operating properly as they show only the highlight but not the actual menu items. The solution will build and run just fine, but things still won't show up properly.
I had a similar issue whereby VS2012 was telling me that I had active (open) files, but the text editor was not displaying them. Clicking on the file(s) in the solution explorer seemingly did nothing. Alt + Tab just cycled through the open files, but still, nothing rendered on screen.
I solved it by clicking on the "WINDOW" menu item and then"Close All Documents". Visual Studio then behaved as expected and opened (and rendered) the files correctly.
This bug was created by mumble 1.2.x, but is fixed in the snapshot versions of 1.3.x. YOu can likely get simular bugs by other software that does DirectX overlay.
I had the same issue in Visual Studio 2012. It was fixed by running a repair of Visual Studio 2012 via Add/ Remove Programs.
The following had no effect:
Closing and reopening a solution
Opening different file types
Restarting Visual Studio
Adding and removing plugins
Resetting options via the 'Reset all Settings' option in Visual Studio's 'Import and Export Settings'
Rebooting windows
I had this problem in Visual Studio 2013. Problem was: extension "Regex Tester". I had to uninstall this extension.

Resources