| T O P I C R E V I E W |
| bartlynn |
Posted - Jul 11 2023 : 4:07:47 PM
Error on startup will loading the Extension in
Microsoft Visual Studio Enterprise 2022 (64-bit) - Preview
Version 17.7.0 Preview 3.0
The 'VaMenuPackage' package did not load correctly.
Error:
SetSite failed for package [VaMenuPackage]Source: 'VaMenuPkg.17' Description: Method not found: 'Microsoft.VisualStudio.Imaging.ImageLibrary Microsoft.VisualStudio.Imaging.ImageLibrary.Load(Microsoft.VisualStudio.Threading.JoinableTaskFactory, System.String, Boolean, Microsoft.VisualStudio.Utilities.ITracer, Microsoft.VisualStudio.Utilities.IStreamStorage`1<System.String>)'.
System.MissingMethodException: Method not found: 'Microsoft.VisualStudio.Imaging.ImageLibrary Microsoft.VisualStudio.Imaging.ImageLibrary.Load(Microsoft.VisualStudio.Threading.JoinableTaskFactory, System.String, Boolean, Microsoft.VisualStudio.Utilities.ITracer, Microsoft.VisualStudio.Utilities.IStreamStorage`1<System.String>)'.
at WholeTomatoSoftware.VisualAssist.VaMenuPackage.c.d()
at System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
at WholeTomatoSoftware.VisualAssist.VaMenuPackage.d(CancellationToken A_0)
at WholeTomatoSoftware.VisualAssist.VaMenuPackage.a.f()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass21_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
at Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck) |
| 30 L A T E S T R E P L I E S (Newest First) |
| feline |
Posted - Aug 25 2023 : 10:44:24 AM
Yes, since it contains several more weeks of new features and bug fixes, and complete features, rather than any partly finished that were in the beta build. Once the release notes go up we will have a clearer sense of exactly what it contains, but this blog post highlights some of the main features:
https://blog.wholetomato.com/2023/08/17/visual-assist-2023-4-preview/ |
| FAN |
Posted - Aug 25 2023 : 08:51:18 AM
Sure, but is it different from the beta you sent out on Monday?
|
| feline |
Posted - Aug 25 2023 : 08:46:19 AM
I agree that two different numbers isn't ideal, but the 2023.4 number gives you the year of release, and which release it was that year. Helpful general information.
The build number, 2500 in this case, is used in the exe file name, so you can tell the build number at a glance. This is also the scheme that goes back a lot further in time, old versions only used this build number, but that did not tell you which year they were released in, so you had to look up the year, to get a sense of if they were covered by your maintenance or not.
This is the new general release, NOT a beta release. The release notes will be along soon, but getting the new build out was more important than waiting on the release notes. |
| barto |
Posted - Aug 25 2023 : 08:29:28 AM
Your different versioning schemes are really confusing. You have a build (2023.4), a version (10.9.2500) and the download filename (va_x_setup2500_0). would be really great if you could decide on a single one.
Also, there's no mention of 2023.4 in the release notes. |
| FAN |
Posted - Aug 25 2023 : 07:16:30 AM
Is it different from the beta version?
|
| feline |
Posted - Aug 25 2023 : 07:10:41 AM
The new version, Build 2023.4, version 10.9.2500 has now been released, and contains the fix for this problem:
https://www.wholetomato.com/downloads |
| feline |
Posted - Aug 24 2023 : 08:06:26 AM
Thank you for the update. So far everyone who has tried the internal build has been happy, so it is looking reliable and stable, so this should work well until the next release comes out. |
| pacioc193 |
Posted - Aug 24 2023 : 07:57:57 AM
quote:
Originally posted by feline
I have emailed you about this pacioc193. The preview made a change which is causing VA problems, but we should have a new release out any day now with the fix for this.
i've received the email and i'm installing it, i will give it a shot and let you know! Thanks |
| feline |
Posted - Aug 24 2023 : 07:16:21 AM
I have emailed you about this pacioc193. The preview made a change which is causing VA problems, but we should have a new release out any day now with the fix for this. |
| pacioc193 |
Posted - Aug 24 2023 : 03:39:11 AM
Same issue here
Microsoft Visual Studio Community 2022 (64-bit) - Preview
Version 17.7.0 Preview 5.0
 |
| Jackie |
Posted - Aug 13 2023 : 09:12:49 AM
Can't wait, I fixed it by modifying IL, can the official reward me with a genuine activation code.
https://bbs.kanxue.com/thread-278399.htm |
| feline |
Posted - Aug 09 2023 : 12:10:08 PM
If you load VS2022 in safe mode, with the command:
"C:\Program Files\Microsoft Visual Studio\2022\Professional\Common7\IDE\devenv.exe" /SafeMode
you will be able to disable or Uninstall Visual Assist from the dialog:
IDE Extensions menu -> Manage Extensions
Safe mode and disable VA is one work around that works for me. A second work around is to run the Visual Studio Installer, on the Visual Studio 2022 line, use the More button to show the pull down list, and you will have the option to "Roll back to previous version". This took a little while for me, and also Uninstalled Visual Assist, so I had to reinstall Visual Assist after doing the roll back.
I am asking what can be done to speed up release of a fix for this problem. |
| sergensv |
Posted - Aug 09 2023 : 09:27:57 AM
quote:
Originally posted by FAN
I have the same problem with the official Visual Studio 2022 version 17.7 released on August 8.
https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes#17.7.0
Same problem: I updated VS to 17.7.0 and catch problem. Repairing of VS and reinstalling of VA doesn't help. |
| FAN |
Posted - Aug 09 2023 : 04:44:09 AM
I have the same problem with the official Visual Studio 2022 version 17.7 released on August 8.
https://learn.microsoft.com/en-us/visualstudio/releases/2022/release-notes#17.7.0
|
| feline |
Posted - Jul 25 2023 : 09:46:02 AM
I don't currently have an estimate for this, but we are aiming for soon. The next build does need to go through internal testing, obviously, first though. |
| bartlynn |
Posted - Jul 25 2023 : 08:26:56 AM
Whats the timeframe for the next release? |
| feline |
Posted - Jul 25 2023 : 06:41:20 AM
Thank you for reporting this. We are working on this, and think we have a solid solution ready for the next release. |
| roman313_ |
Posted - Jul 25 2023 : 05:17:07 AM
Error on startup will loading the Extension in
Microsoft Visual Studio Enterprise 2022 (64-bit) - Preview
Version 17.7.0 Preview 4.0
The 'VaMenuPackage' package did not load correctly.
Steps to try to fix:
devenv.exe /Setup - cant't help
Re-install Visual Assist - can't help
SetSite failed for package [VaMenuPackage]Source: 'VaMenuPkg.17' Description: #1052;#1077;#1090;#1086;#1076; #1085;#1077; #1085;#1072;#1081;#1076;#1077;#1085;: "Microsoft.VisualStudio.Imaging.ImageLibrary Microsoft.VisualStudio.Imaging.ImageLibrary.Load(Microsoft.VisualStudio.Threading.JoinableTaskFactory, System.String, Boolean, Microsoft.VisualStudio.Utilities.ITracer, Microsoft.VisualStudio.Utilities.IStreamStorage`1<System.String>)".
System.MissingMethodException: #1052;#1077;#1090;#1086;#1076; #1085;#1077; #1085;#1072;#1081;#1076;#1077;#1085;: "Microsoft.VisualStudio.Imaging.ImageLibrary Microsoft.VisualStudio.Imaging.ImageLibrary.Load(Microsoft.VisualStudio.Threading.JoinableTaskFactory, System.String, Boolean, Microsoft.VisualStudio.Utilities.ITracer, Microsoft.VisualStudio.Utilities.IStreamStorage`1<System.String>)".
#1074; WholeTomatoSoftware.VisualAssist.VaMenuPackage.c.d()
#1074; System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start[TStateMachine](TStateMachine& stateMachine)
#1074; WholeTomatoSoftware.VisualAssist.VaMenuPackage.d(CancellationToken A_0)
#1074; WholeTomatoSoftware.VisualAssist.VaMenuPackage.a.f()
--- #1050;#1086;#1085;#1077;#1094; #1090;#1088;#1072;#1089;#1089;#1080;#1088;#1086;#1074;#1082;#1072; #1089;#1090;#1077;#1082;#1072; #1080;#1079; #1087;#1088;#1077;#1076;#1099;#1076;#1091;#1097;#1077;#1075;#1086; #1088;#1072;#1089;#1087;#1086;#1083;#1086;#1078;#1077;#1085;#1080;#1103;, #1075;#1076;#1077; #1074;#1086;#1079;#1085;#1080;#1082;#1083;#1086; #1080;#1089;#1082;#1083;#1102;#1095;#1077;#1085;#1080;#1077; ---
#1074; System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
#1074; System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
#1074; Microsoft.VisualStudio.Shell.AsyncPackage.<>c__DisplayClass21_0.<<Microsoft-VisualStudio-Shell-Interop-IAsyncLoadablePackageInitialize-Initialize>b__1>d.MoveNext()
--- #1050;#1086;#1085;#1077;#1094; #1090;#1088;#1072;#1089;#1089;#1080;#1088;#1086;#1074;#1082;#1072; #1089;#1090;#1077;#1082;#1072; #1080;#1079; #1087;#1088;#1077;#1076;#1099;#1076;#1091;#1097;#1077;#1075;#1086; #1088;#1072;#1089;#1087;#1086;#1083;#1086;#1078;#1077;#1085;#1080;#1103;, #1075;#1076;#1077; #1074;#1086;#1079;#1085;#1080;#1082;#1083;#1086; #1080;#1089;#1082;#1083;#1102;#1095;#1077;#1085;#1080;#1077; ---
#1074; System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
#1074; Microsoft.VisualStudio.Services.VsTask.RethrowException(AggregateException e)
#1074; Microsoft.VisualStudio.Services.VsTask.InternalGetResult(Boolean ignoreUIThreadCheck)
Visual Assist work OK, but NO ICONS in menu |
| Dusan |
Posted - Jul 20 2023 : 04:49:35 AM
This issue is happening when VA can't find our images in the image cache.
In that case VA tries to call ImageLibrary.Load function with declaration: ImageLibrary.Load(JoinableTaskFactory, string, [bool], [ITracer], [IStreamStorage]).
However this function has changed in Preview 3.0 to: ImageLibrary.Load(JoinableTaskFactory, string, [bool], [ITracer])
so framework can't find this function, because we compile against DLLs provided for previous VS version.
For those having administrator rights running Visual Studio with /setup switch could help.
This should force Visual Studio to load our images to the image library cache an thus prevent us from Load call.
For those without administrator rights this may not work and will have to wait for the fix.
The fix is already submitted so it should be included in next release if it will pass the testing cycle. |
| feline |
Posted - Jul 19 2023 : 12:15:34 PM
Thank you for the update. We believe we have a fix for preview 3.0, so hopefully the same fix works correctly for preview 4.0. We are hoping to get this released fairly soon. Obviously we don't want the next non preview release to have this problem with VA. |
| bartlynn |
Posted - Jul 19 2023 : 10:51:56 AM
Still an issue with Preview 4 |
| feline |
Posted - Jul 14 2023 : 09:31:38 AM
I have been chasing this problem, and one of our developers is currently looking into it. No updates yet, but hopefully we will have something soon. No idea if this is the same problem as we are having with the preview version though, since the trigger conditions are a bit different. |
| FAN |
Posted - Jul 14 2023 : 08:50:46 AM
I'm talking about the bug that was reported in case 149606/149646.
I received an email that your development team was able to reproduce the bug and was working on it, but I have not heard anything since.
|
| feline |
Posted - Jul 14 2023 : 08:26:04 AM
Code Inspection is working normally for me in VA 2476.0 in VS2022 version 17.6.5, I am seeing many code inspection results returned in my tests.
But, I am not seeing any at all returned in preview 3.0, same version of VA. I have noted this on the bug report, but it will take a day or two to get this looked at, and then we need to fix the problem, once we understand it. |
| FAN |
Posted - Jul 14 2023 : 03:06:14 AM
For VA 2476, Code Inspection does not work properly for Visual Studio Preview and Visual Studio Release 17.6.5.
Is there an update for this problem?
|
| bartlynn |
Posted - Jul 13 2023 : 1:22:25 PM
Maybe its an easier one to solve since it was broken between versions. |
| feline |
Posted - Jul 13 2023 : 11:50:06 AM
Well, so much for that theory. I am seeing the same error:
case=149749
if you want to keep on using VA with this preview, I would suggest uninstalling VA, and installing VA 2476 instead, which doesn't seem to have this problem, at least not based on a few quick tests. |
| feline |
Posted - Jul 13 2023 : 08:38:17 AM
Installing preview 3 now, to see if I get any problems.
For now though, can you please try going into:
IDE Extensions menu -> Manage Extensions
and Disable Visual Assist, which will require an IDE restart to take effect. Can you then go back into this dialog and Enable Visual Assist, which will again require an IDE restart to take effect.
Sometimes when odd errors show up on start up this can and does fix them, so its possible it will help.
Are you seeing any form of pattern to this problem? Or does it seem quite random? |
| bartlynn |
Posted - Jul 12 2023 : 09:37:38 AM
It still does happen occasionally when I open VS. |
| bartlynn |
Posted - Jul 11 2023 : 4:28:17 PM
After a reboot, it seems OK, but I will continue to watch it. |
