Just a quick note to let you know that we are aware of a blocking issue while using the latest version of VA in Preview 4. We offered initial beta support for 3.x, however we do not recommend installing Visual Assist on the latest preview as the hangs will render the IDE unusable. We’re working on it and hope to have an update out soon.
Even though each release offers new challenges and setbacks we’re excited for the move to 64bit and the future of Visual Assist when VS 2022 is fully baked. Thanks for your patience!
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.
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 [email protected]
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..
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 ?
Hi Louka, we actually just released a new version with support for more of the previews: https://support.wholetomato.com/default.asp?W404#2435