Comments for Tomato Soup https://www.wholetomato.com/blog Visual Assist Team Blog Thu, 11 Apr 2024 18:04:41 +0000 hourly 1 https://wordpress.org/?v=6.4.5 Comment on Prevent debugger from stepping into unwanted functions in Visual Studio by What must I do for visual studio 2017 to use the natstepfilter file to avoid stepping into std library functions and class methods? – Windows Questions https://www.wholetomato.com/blog/2020/08/18/prevent-debugger-from-stepping-into-unwanted-functions-in-visual-studio/#comment-132 Mon, 14 Mar 2022 22:39:54 +0000 http://blog.wholetomato.com/?p=1724#comment-132 […] I have tried both ways with and without escaping the colon character but neither seems to work. https://www.wholetomato.com/blog/2020/08/18/prevent-debugger-from-stepping-into-unwanted-functions-in-vi… […]

]]> Comment on Visual Studio 2022 Support! by Improving Whole Tomato: We need your opinion – Tomato Soup https://www.wholetomato.com/blog/2021/11/23/visual-studio-2022-support/#comment-124 Wed, 15 Dec 2021 18:00:45 +0000 https://blog.wholetomato.com/?p=2028#comment-124 […] ← Visual Studio 2022 Support! […]

]]> Comment on Visual Assist 2021.4 is released! (And notes on Visual Studio 2022) by Visual Studio 2022 Support! – Tomato Soup https://www.wholetomato.com/blog/2021/11/02/visual-assist-2021-4-is-released-and-notes-on-visual-studio-2022/#comment-123 Tue, 23 Nov 2021 10:44:08 +0000 https://blog.wholetomato.com/?p=2012#comment-123 […] doing to support VS2022, with beta support for Previews 3, skipping 4 due to a breaking bug, and 5, 6, and 7/RC. We released Visual Assist 2021.4 shortly before Visual Studio 2022 was released, and many of you […]

]]> Comment on Visual Studio 2022 preview version 4 support by Visual Studio 2022 Support! – Tomato Soup https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-122 Tue, 23 Nov 2021 10:44:06 +0000 https://blog.wholetomato.com/?p=2008#comment-122 […] about the work we’ve been doing to support VS2022, with beta support for Previews 3, skipping 4 due to a breaking bug, and 5, 6, and 7/RC. We released Visual Assist 2021.4 shortly before Visual Studio 2022 was […]

]]> Comment on Visual Assist support for Visual Studio 2022 Previews! by Visual Studio 2022 Support! – Tomato Soup https://www.wholetomato.com/blog/2021/08/12/visual-assist-support-for-visual-studio-2022-previews/#comment-121 Tue, 23 Nov 2021 10:44:04 +0000 https://blog.wholetomato.com/?p=1996#comment-121 […] past nine months about the work we’ve been doing to support VS2022, with beta support for Previews 3, skipping 4 due to a breaking bug, and 5, 6, and 7/RC. We released Visual Assist 2021.4 shortly […]

]]> Comment on Visual Studio 2022 preview version 4 support by Visual Assist 2021.4 is released! (And notes on Visual Studio 2022) – Tomato Soup https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-120 Tue, 02 Nov 2021 19:14:39 +0000 https://blog.wholetomato.com/?p=2008#comment-120 […] it’s important to many of you, and we hope you’ve enjoyed seeing VAX working in many of the Visual Studio 2022 Previews. We expect VS2022 to be released very soon. In fact, as we were […]

]]> Comment on Visual Assist support for Visual Studio 2022 Previews! by Visual Assist 2021.4 is released! (And notes on Visual Studio 2022) – Tomato Soup https://www.wholetomato.com/blog/2021/08/12/visual-assist-support-for-visual-studio-2022-previews/#comment-119 Tue, 02 Nov 2021 19:14:37 +0000 https://blog.wholetomato.com/?p=1996#comment-119 […] to us, because we understand it’s important to many of you, and we hope you’ve enjoyed seeing VAX working in many of the Visual Studio 2022 Previews. We expect VS2022 to be released very soon. In fact, as […]

]]> Comment on Visual Studio 2022 preview version 4 support by Kyle Wheeler https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-118 Tue, 02 Nov 2021 14:31:16 +0000 https://blog.wholetomato.com/?p=2008#comment-118 In reply to Louka Outrebon (@LocaLouka).

Hi Louka, we actually just released a new version with support for more of the previews: https://support.wholetomato.com/default.asp?W404#2435

]]> Comment on Visual Studio 2022 preview version 4 support by Louka Outrebon (@LocaLouka) https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-117 Tue, 02 Nov 2021 09:02:53 +0000 https://blog.wholetomato.com/?p=2008#comment-117 As VS is out in 4 days and you’ve not been updating since 2 months, could you give us some insights as to when you think VS will be ready ?

]]> Comment on Visual Studio 2022 preview version 4 support by test account (@1234temp) https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-115 Wed, 22 Sep 2021 01:53:43 +0000 https://blog.wholetomato.com/?p=2008#comment-115 In reply to Kyle Wheeler.

I have a fix/workaround: block PerfWatson2.exe in your app locker. Then VAX is completely usable in VS 2022 Preview 4.1.

C:\Program Files\Microsoft Visual Studio\2022\Preview\Common7\IDE\PerfWatson2.exe

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers etc..
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\Safer\CodeIdentifiers etc..

]]> Comment on Visual Studio 2022 preview version 4 support by Kyle Wheeler https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-114 Fri, 17 Sep 2021 02:18:40 +0000 https://blog.wholetomato.com/?p=2008#comment-114 ve produced for vs2022 is beta and should be treated as such while we work out the kinks. Feel free to email me directly for any support Kyle.wheeler@wholetomato.com]]> In reply to test account (@1234temp).

Thanks for being an early adopter. We will take care of you however this shakes out. Unfortunately due to the beta/preview status of all things vs2022 we are at the whim of Microsoft. Of course we are actively working with them and behind the scenes to resolve any issues but everything we’ve produced for vs2022 is beta and should be treated as such while we work out the kinks. Feel free to email me directly for any support Kyle.wheeler@wholetomato.com

]]> Comment on Visual Studio 2022 preview version 4 support by test account (@1234temp) https://www.wholetomato.com/blog/2021/09/16/visual-studio-2022-preview-version-4-support/#comment-113 Fri, 17 Sep 2021 02:15:11 +0000 https://blog.wholetomato.com/?p=2008#comment-113 It’s unfortunate that VS 2022 Preview 4.0 doesn’t provide reverting to a previous Preview release like 3.1. I have a VAX license with no more support updates available, but it had VS 2022 support. Hopefully the fix won’t mean paying another $129 for a VAX license because I can’t revert VS 2022 Preview 4.0.

]]> Comment on Technical Deep Dive: Reducing Memory Consumption in Visual Assist build 2393 by Visual Assist support for Visual Studio 2022 Previews! – Tomato Soup https://www.wholetomato.com/blog/2020/12/17/technical-deep-dive-reducing-memory-consumption-in-visual-assist-build-2393/#comment-111 Thu, 12 Aug 2021 17:48:07 +0000 http://blog.wholetomato.com/?p=1790#comment-111 […] others, last November we greatly reduced the in-process memory usage largely through (spoiler: the full blog is worth reading) use of memory-mapped […]

]]> Comment on Busy Busy Busy! by Kyle Wheeler https://www.wholetomato.com/blog/2021/06/21/busy-busy-busy/#comment-110 Tue, 10 Aug 2021 22:45:47 +0000 https://blog.wholetomato.com/?p=1973#comment-110 s new and more details to come later this week. ]]> In reply to Parag Paul (@rahiakil).

Check out our downloads page. Preliminary beta support is live! What’s new and more details to come later this week.

]]> Comment on Busy Busy Busy! by Parag Paul (@rahiakil) https://www.wholetomato.com/blog/2021/06/21/busy-busy-busy/#comment-109 Tue, 10 Aug 2021 22:35:04 +0000 https://blog.wholetomato.com/?p=1973#comment-109 We are waiting eagerly for the Visual Studio 2022 support as it is the first VS build with 64 bit support and some of our binaries are just large and that needs this kind of debugging power. When can we find the new VS Assist build for VS 2022

]]> Comment on Technical Deep Dive: Reducing Memory Consumption in Visual Assist build 2393 by Unreal Engine ‘Quality Of Life’ in Visual Assist 2021.2 – Tomato Soup https://www.wholetomato.com/blog/2020/12/17/technical-deep-dive-reducing-memory-consumption-in-visual-assist-build-2393/#comment-108 Thu, 15 Jul 2021 17:52:30 +0000 http://blog.wholetomato.com/?p=1790#comment-108 re starting to blog in greater detail about some of what we change — our December blog about reducing memory usage started this — and this time we’ll dig a bit more into two changes improving using Unreal […]]]> […] and release blogs, we’re starting to blog in greater detail about some of what we change — our December blog about reducing memory usage started this — and this time we’ll dig a bit more into two changes improving using Unreal […]

]]> Comment on A Brief Introduction To Clang-Tidy And Its Role in Visual Assist by Bartłomiej Filipek https://www.wholetomato.com/blog/2021/01/08/a-brief-introduction-to-clang-tidy-and-its-role-in-visual-assist/#comment-105 Sat, 16 Jan 2021 16:00:08 +0000 http://blog.wholetomato.com/?p=1755#comment-105 In reply to Andrew Truckle.

Thanks for the question and for using VA! 🙂
I’d say that VAX code Inspections are far better than default Clang Tidy Settings, and what’s more the user experience is much nicer and easier. Yet, you can experiment with Cland-Tidy and maybe check some other “inspections” that are not yet supported by VAX.

]]> Comment on A Brief Introduction To Clang-Tidy And Its Role in Visual Assist by Andrew Truckle https://www.wholetomato.com/blog/2021/01/08/a-brief-introduction-to-clang-tidy-and-its-role-in-visual-assist/#comment-104 Sat, 16 Jan 2021 11:23:05 +0000 http://blog.wholetomato.com/?p=1755#comment-104 Question: If I am using the VAX Code Inspection system, is there actually any benefit to activating the Clang-Tidy setting in VS Code Analysis?

]]> Comment on Technical Deep Dive: Reducing Memory Consumption in Visual Assist build 2393 by David Millington https://www.wholetomato.com/blog/2020/12/17/technical-deep-dive-reducing-memory-consumption-in-visual-assist-build-2393/#comment-103 Sun, 20 Dec 2020 14:48:56 +0000 http://blog.wholetomato.com/?p=1790#comment-103 In reply to adequat49.

Thanks for the comment!

Yes, the 4GB has to be shared by all of Visual Studio and its extensions — that’s what spurred this work. And we don’t use IPC at all.

We called it ‘out of process’ originally because we were planning multiple processes with IPC, but the term stuck and we didn’t feel it particularly inaccurate because when the string data is in a memory mapped file, that data as a whole does not take up this process’s address space, until portions of it are mapped in. That’s what we do (about 40MB is permanently mapped in.) So if we have, say, 200MB of string data, only 40MB are in-process (or, in-process-address-space.) Perhaps ‘out of process address space’ is a more accurate term.

And — thanks for using VA! 🙂

]]> Comment on Technical Deep Dive: Reducing Memory Consumption in Visual Assist build 2393 by adequat49 https://www.wholetomato.com/blog/2020/12/17/technical-deep-dive-reducing-memory-consumption-in-visual-assist-build-2393/#comment-102 Sat, 19 Dec 2020 12:55:32 +0000 http://blog.wholetomato.com/?p=1790#comment-102 You’re mistaken when you say: “after all, the memory is not in our process.”
Yes, it is. There are 4 GB of space to share by any stakeholder in the same process. For example, if there are four visual studio addins to use the same technique as yours, they will have to share the 4 GB memory; they can’t have 4 GB each.
Therefore, apparently, what you did, is a dedicated memory manager to replace malloc/free. This can indeed increase performance if it is well-tailored to your needs.
But this can’t be called IPC in any way.
Loving VA btw 😉

]]>