Ok I have an update. I took the chance and reinstalled both docker desktop and Visual Studio on my Windows PC clean (no admin usage anywhere by the way). With fresh installs I have now run into the same error you are experiencing.
This means either there is some additional setup step somewhere that hasn’t been documented that is required to get this working. Or even more likely a new version of either Visual Studio or Docker Desktop has broken compatibility with our IDE extension.
Let me report this to our IDE team for further investigation.
Interesting. I started to drag out my personal laptop and install everything on it as a crosscheck but then found that Docker can’t support the Hyper-V back end on Windows 10 Home. You can put WSL2 on Windows 10 Home and there’s a Docker version for that but not the same. Since it was my personal machine I decided against it.
Portainer is also showing an update is available. I have not installed it and truthfully I don’t have a clue how to do the update. It’s certainly more than a point and click. However, I believe that Portainer has nothing to do with this problem.
Looking forward to what your IDE team comes up with.
The issue has been reported to the IDE team, quick testing on their end has confirmed the issues both you and I experienced. Initial assumption seems to be that the latest Visual Studio update may have broken compatibility. Which is why I only experienced the issue when I reinstalled Visual Studio which forced the latest version on my system.
So preemptively the team will start working on this ASAP since it is a breaking bug. We don’t know the full extent of the effort since more investigation may be required. But in any case as soon as a fix is available then I’ll let you know.
VS 2019 just sent me another update notice. We have been working on 16.7.1 through these errors but they have released 16.7.2. You might want to tell your IDE guys to jump on to 16.7.2.
Ok good news, seems like the team was able to isolate the issue and get a fix prepared rather quickly. As a side note the problem was indeed the 16.7 Visual Studio update which changed some library definitions that our extension accesses.
This early release version is built whenever the team pushes new changes. Meaning it constantly changes and is not “stable”. Please note that when installing this early access version there are expected to be bugs/lack of documentation and little to no testing on our side on the features that differ from the stable release.
That being said this early access release should have the fix for this issue which we did quickly verify and the fix seems to work.
In order to install this you must first uninstall the stable version of the extension as Visual Studio can’t support having both installed at the same time. Also since this includes the fix for this issue, this will require Visual Studio version 16.7.
With all that being said please try it out if you don’t mind and feel free to give any feedback about the early access or in this specific case let us know please if the fix that the team did still has some issues.
Looks like the developers didn’t specify 16.7 but specifically 16.7.0. 16.7 is now up to 16.7.2. Looking online I can’t find a way to get back to 16.7.0. Microsoft keeps pushing you forward…
I got a paid license from MSFT so now can download any version. Actually didn’t have any luck installing the early release with 16.7.0 either. I think that’ just the earliest version that’s supposed to work. I also tried installing the Extension Development section since somebody said that would get you the Component.CoreEditor but that didn’t work either.
Maybe we can go at this a different way since I can download multiple versions. What was the version that the regular Toradex VS extension in the “getting-started” installed on?
I was able to recreate the same issue of not being able to install the “Early Access” version on my 16.7.2 Visual Studio. Seems we had a classic issue of it worked on some of our team’s windows machines but not everyone’s. But the team was informed again so they’re looking at the issue.
As for past versions that worked with the getting-started. I remember before i did a fresh reinstall of Visual Studio I had version 16.6.something and that worked. Also I believe the team’s investigation found that it was the 16.7 release that broke compatibility.
I installed VS 2019 16.6.5 Professional and was able to install the VS extension. The HelloWorld will go through the program a couple of times buth then I can’t seem to make it run again without getting all the way out of VS and back in again. The Torizon toolbar grays out and there aren’t any commands related to Torizon anymore.
That worked! I was able to install it on both the VS 2019 16.7.2 Professional and Community editions. I have run it on the VS 2019 16.7.2 Professional at this point. You 'da man! Please convert it to an answer
I still have the install issue on my side, but the team was able to isolate and fix the issue, I believe they just need to push the changes to the marketplace which should happen probably by Monday.
Sorry to interrupt, I’ve been following this topic closely because I had the same issue. I was able to get the “Early Access” version working by modifying the attached files (unzip the vsix, replace the files, zip it again and change the extension back to vsix). I actually followed this link from stackoverflow.
I’ve just been trying to see what I can install where today. I just tried installing the new 1.2.22 that is in the Visual Studio Marketplace on 16.7.2 Community but it has the same problem as the one from yesterday about installing. I suspect that Andy’s fix will work with it too.
Please see my above comment to your question, the fix is done on our side but we still need to push it to the marketplace. The last time the early access was updates was yesterday we haven’t pushed Today’s test build yet.
The early access version I got yesterday was 1.2.21. I actually got a update notice in VS this morning and checked that there was a 1.2.22. If I check the one I got going with Andy’s fix earlier today it was the 1.2.21 because I’m the one that merged the fix and I checked it.
The 1.2.22 has the same problem we were fighting yesterday. I went in and did the same modifications that Andy did and got it to install on the VS2019 16.7.2 Community edition. It’s running now.
With respect to the graying out and such probably my operator error somewhere. I can’t recreate it at the moment. I think I may have clicked something in the Build menu that wasn’t Torizon and it tried to make a local machine version of the build and which point the Torizon menu items grayed out. Don’t know. I’ll keep an eye out.
If the IDE guys come up with something past 1.2.22 I’ll put that in. Thanks.
