CodePush CLI Migration (to AppCenter) - visual-studio-app-center

I currently use CodePush for my Cordova app. Love it. Microsoft is moving it to AppCenter, and here's the migration guide.
The migration guide notes that the old CLI will be retired in October 2018:
we are commited to maintain the CLI through September 2018. You are free to continue using the CLI, but all features besides release and viewing metrics will be disabled in Late March 2018. Finally, the CodePush CLI will be retired in Mid October 2018.
My question is if this plan is still accurate? I know the original plan was to make a new Cordova SDK in February 2018, which was pushed back and no ETA is known. Is the old CodePush CLI still going to be retired in October? From what I can tell core things (like getting install metrics) are still not available in the new CLI. I really don't want to use the AppCenter CLI for some things and log into the AppCenter UI for others.

I don't believe a new CodePush SDK is going to be made available. It is also not on their roadmap:
https://learn.microsoft.com/en-us/appcenter/general/roadmap
This image used to be on the AppCenter website showing that the CLI will be deprecated starting with reduced functionality in favor of the AppCenter UI.

Related

Deprecation of all previous Azure Application Insights NuGet packages

All previous versions, of the various Microsoft.ApplicationInsights.* packages on nuget.org have all switched to being deprecated. This feels unusual for a minor release, and it's not acknowledged in the release notes. Is there a reason for this?
e.g. https://www.nuget.org/packages/Microsoft.ApplicationInsights.AspNetCore
To answer my own question for anyone else that might be wondering if they need to upgrade Application Insights packages, the short answer is no. You can keep on using the version you are on with the usual consideration for the patch and minor release notes.
This is a recent move by the Application Insights team to comply with the Azure SDK lifecycle and support policy that states:
or has been superseded by a more recent release. In both cases, the current library is deprecated in favor of a newer library.
The main driver, is that support requests are typically resolved by updating to the latest SDK version, so only 'supporting' the latest version ensures we all try that first before teams commit resources to support.
Source: Application Insights GitHub issue.

Not able to add new azure function in VSCode

I opened my project repo as usual , then I noticed that I can't add new azure function
the + icon disappeared:
I don't know how to get it back ?
After reproducing the same by downloading the latest July 2022 - version 1.70 we faced the same issue. This might be a bug that is seen in the latest release.
You can follow the updates from the tickets that I have raised over Github - Azure Functions Support.
However, as an alternative, you can install the previous stable June 2022 (version 1.69).

VS2017: why cannot select Azure Functions for NetCore?

So I researched a lot about trying to create an Azure Functions project. Downloaded latest extensions, updated my VS2017 community, etc.
I still only get two options NetFw and NetStandard.
How can I use NetCore as the target?
For now .Net Core TargetFramework is not supported yet.
See the comment from Azure Functions team.
We expect to have manual steps that you can try by mid October, and our goal is to have all relevant template/tooling updates complete and deployed by the end of October.
Update
v2 Function project with .NET Core TargetFramework(netcoreapp2.1) support has been available, make sure VS >= 15.8(right now 15.8.8) and Azure Function and Web Jobs Tools(On VS menus>Tools>Extensions and Updates) is latest(15.10.2046 right now).

Automating with Puppet on GCE without `gcutil` (deprecated)

I am trying to automate an instance using Puppet in Google cloud but unfortunately got an error. I had done this earlier with your help but the settings seems to be changed.
ERROR: 'gcutil' has been deprecated and is no longer part of Cloud SDK distribution.
ERROR: Please use 'gcloud compute' instead.
The change from gcutil to gcloud was merged recently on GitHub on 21 July 2015 and released in puppetlabs/gce_compute 1.0.0 on 29 July 2015, so you should upgrade to get this change.

Jobs from an earlier version of the Azure WebJobs SDK have been detected

I'm using web-jobs SDK pre-release version and from few minutes ago Im getting this warning message:
Jobs from an earlier version of the Azure WebJobs SDK have been detected. Please upgrade the jobs to the latest version in order to see their status in the dashboard. Please visit this article for more information about the Azure WebJobs SDK.
I would be thankful if you help me with this.
Later edit: the link should work now
The page for that link is not yet live. It will be published soon, sorry for the inconvenience.
Meanwhile, to upgrade, get the latest WebJobs SDK packages (notice the package names changed so you might want to remove the old ones):
http://www.nuget.org/packages/Microsoft.Azure.Jobs/0.3.0-beta
http://www.nuget.org/packages/Microsoft.Azure.Jobs.Core/0.3.0-beta
Also notice that some attribute names changed:
Where are Azure WebJob's BlobInput and BlobOutput classes?

Resources