ML.Net Model Builder 2022 updates - ml.net

Every time I update VS 2022, I get a notification that ML.Net Model builder needs an update... However its the same version that keeps getting re-updated.
It appears that with every VS 2022 I have to udpate this extension to the same version over and over again. This screenshot is one I took two days ago on the 14th (vs 2022 17.0.3) and today I did the VS 2022 17.0.4 update and low and behold I now have to update ML.Net and its the same version changes as it was 2 days ago and earlier....
Is this a weird bug with VS 2022?
12/20/2021 This happened again... the PKGDEF extension required an update and during that update ML.NET was downgraded again and so required another ML.NET update back to the 16.7.6.2152701 version. This is really getting annoying...
12/22/2021 This happened again... the PKGDEF extension required an update and during that update ML.NET was downgraded again and so required another ML.NET update back to the 16.7.6.2152701 version.
Thoughts?

Related

Cannot load facet Django in Pycharm community version, but no error in professional version

I started learning Django by building a simple project with Pycharm community version first, then in the middle of the development, I switched to the professional version. After the trial version expired, I moved back to the community version.
Now when I am using the community version, Pycharm shows event error:
Error Loading Project: Cannot load facet Django
If I try the professional version, it's successfully loaded.
Can anybody help?
Click "Details..." in the warning popup and answer "Yes" to the suggestion to ignore the facet or manually remove <facet type="django" name="Django"> node and all it's children from .idea/<project_name>.iml stored in your project root.

Visual Studio 2017 blank project open dialog and hang

I installed 2017 and used it for some time (months). After one of the updates, I started having trouble in the file browser window not navigating to other folders without hanging. I can't navigate or choose a file. the app is hung here. I have left it up for several minutes and it stays hung there. I have to kill it from Task Manager in the current version; in prior versions it hung the system and I had to power off. I saw similar problems posted and a reply that indicated it was reproduced and would be fixed. I starting using VS 2015 again in the meantime. That was a few release ago. I had hopes that the most recent one (now on 15.7.3) might fix it since it was fairly large. It made me have a different issue in the same dialog. Now it is blanked out and only VS 2017 is hung. That's a little better since I don't have to restart my system every time I try to run it. But I really need to move to VS 2017.
Any suggestions would be appreciated. I have uninstalled and re-installed several times and tried uninstalling and reinstalling the more recent .net versions.
Windows 10 Enterprise, kept current with Windows Update, 32G RAM
On trying to browse for a solution, this comes up.

Visual Studio 2017 RC - Prerelease has ended

I get the following message and cannot proceed to do any other work within Visual Studio 2017 RC : This prerelease has ended. This prerelease has expired. Thank you for your participation. Upgrade to the latest version of this product to keep working without interruption.
Upgrade your prerelease Check for an updated license.
No other options on the screen work. ie. "Upgrade your prerelease" or "Check for an updated license. I currently have a valid MSDN license, so this should not be an issue.
Update: The VS team has fixed the issue on their end. You do not need to perform these steps, simply check for an updated license. (I'm leaving this answer up in case there is a regression in the future.)
Install Fiddler and turn on HTTPS decryption. Create an AutoResponder rule that matches:
regex:(https://app.vssps.visualstudio.com/_apis/Licensing/ClientRights/VisualStudio.*)prerelease(.*)
And replaces with:
$1release$2
With that rule enabled, check for a license again. You should wind up with a trial license that will last until April.
Fiddler should look similar to this when configured (intercepted requests shown on the left):
My HTTPS configuration in Tools->Telerik Fiddler Options looks like:
This was a server side bug that Microsoft has now fixed.
See the Visual Studio Team's response
Only solution I've found at the moment is to change the date to the past by a year. For example today's date is 2ndJune2017, if you change the date to 2ndJune2017 and open Vs 2017 RC version, it should work.
I won't consider this as a proper fix but its the only solution worked for me.

Android Studio: Most activity code templates not available

I have removed and installed Android Studio to 0.5.2, updated all my JDK's and basically started from scratch after abandoning development for a while.
I have seen that there are many code templates that a lot of new videos dealing with Android Studio have; however, I don't have them.
How do I get them and install them if needed?
Android Studio is a Preview product (not-yet-beta) and is under heavy active development. There are canary channel releases almost every week. 0.5.2 was released back in mid March and the other templates that you see have been added since that time. If you want to switch to the canary channel and update to the latest canary build (0.5.9, released last week) then you can follow the directions here to do so: http://tools.android.com/preview-channel#TOC-Android-Studio-Previews

dotless build task error

After recently upgrading to the latest version of dotless on nuget, I'm now getting build errors.
I have dotless set up as a build task, as per https://stackoverflow.com/a/2181543/435460
It used to work, but when I recently updated to the latest version on nuget I now receive the error dotless 1.3.0.5 has stopped working when I attempt to build, resulting in my build failing.
Is there a way to get this working again? I've already done some preliminary google investigating and have come up short.
It looks like this was caused on our machines by something removing the .NET 3.5 Framework - the dev had been having other issues, and I think removed 4.5, and something around that cleaned out 3.5 next time he rebooted.
Re-installing .NET 3.5 seemed to have resolved the issue.