For my project, I need .NET Core 2.2. The Chocolatey package repository states that .NET Core 2.2.8 is the most recent version of .NET Core 2.2 available. I can install this package with choco install dotnetcore --version 2.2.8 -m. But when 2.2.9 will be released, I will still be on 2.2.8, because I specified that specific version. What command do I need to have .NET Core 2.2 updated to a new minor version when I issue choco upgrade all?
EDIT: I do not want to upgrade to .NET Core 3.x when I issue choco upgrade all, because I have some projects that depend on it. Instead, I explicitly want Chocolatey to upgrade to .NET Core 2.2.9 if it will be released
While I think this belongs better on Super User, based on what is implied by using side by side installations of a package, if you want a new version of that package, use choco install -m to install the newer version of that package. Based on your experience of choco upgrade all upgrading one of your side by side packages however, you may want to inquire on the Chocolatey issue tracker as to what the recommended method of upgrading your other packages would be here.
Related
I created a new project in Visual Studio 2019 Community using the ASP.NET Core Web Application template
and selecting ASP.NET Core 5.0 and ASP.NET Core with React.js
After the project was created, I switched to the ClientAppfolder and executed npm update. After that, npm outdated gives me:
Package Current Wanted Latest Location
cross-env 5.2.1 5.2.1 7.0.2 webapplication1
eslint 6.8.0 6.8.0 7.14.0 webapplication1
eslint-config-react-app 5.2.1 5.2.1 6.0.0 webapplication1
eslint-plugin-flowtype 4.7.0 4.7.0 5.2.0 webapplication1
merge 1.2.1 1.2.1 2.1.0 webapplication1
react 16.14.0 16.14.0 17.0.1 webapplication1
react-dom 16.14.0 16.14.0 17.0.1 webapplication1
react-scripts 3.4.4 3.4.4 4.0.0 webapplication1
rimraf 2.7.1 2.7.1 3.0.2 webapplication1
typescript 3.9.7 3.9.7 4.1.2 webapplication1
Comparing wanted and latest version it seems like the templates are outdated. Are there any updates for the official templates or do I have to check manually which packages can be upgraded without breaking things?
UI world is extremely dynamic. So I'd say it's a fact that UI packages will get updates often and MS will never be able to keep this "Zoo" up to date.
In my production experience - I usually setup UI app template myself - using webpack, typescript etc, depending on customer needs. And using SPA configuration in Asp.NET Core it's easy to make any app build within general pipe. But it's only for cases when I need it to be part of ASP.NET Core Web App. From my point of view, however, it's more correct to host SPA stuff separately from Asp.NET Core backend.
Talking about ASP.NET Core Web App template from MS (which was mentioned) - for UI it's based on create-react-app (https://github.com/facebook/create-react-app). You can check that in "package.json" searching for react-scripts. You can start upgrading from this entry point. And then - check what's left and upgrade the rest if needed.
p.s. By the way, some time ago MS tried to keep up to date Windows based docker image with NodeJS installed. But they ended up this support as well because of NodeJS frequent updates and versions list.
I want to upgrade React Native Debugger from version 0.10.0 to version 0.10.2, but clicking to upgrade when the program itself prompts me isn't working because (as they indicate on their page), there's a bug that prevents this upgrade. People have suggested "manually" upgrading or using brew cask reinstall react-native-debugger. The latter doesn't work, so I was wondering how you go about manually upgrading a package like this?
You can go to the release page https://github.com/jhen0409/react-native-debugger/releases/tag/v0.10.2 and download the appropriate .dmg file (for MacOS) from there. Afterwards you can just install it like any regular .dmg.
I tried to install the latest angularjs (1.5.5) via bower. It was taking already an hour so I tried installing an earlier version (1.5.0). It actually worked, but bower also tried to install 1.6.2. Now its taking forever for the build to finish. Is there something that I have missed along the installation?
installation via bower installation
I did my project in cakePHP 3.0. By updating the composer my project converted into cakePHP 3.2. I want to rollback from 3.2 to 3.0. I tried rollback options too,that is also not working. How to rollback 3.2 to 3.0 ?
The rollback command supporty by composer is for the composer itself, ie it rolls back your composer installation to an earlier version, not anything that might have been installed via composer.
To change the version of the cakephp/cakephp dependency, simply require the new version with a version constraint that doesn't match 3.1 and above, so in your case, if you want to switch back to the 3.0.x branch, you could just run
$ composer require cakephp/cakephp:"~3.0.0"
The ~3.0.0 constraint will match >= 3.0.0 && < 3.1.0. See Composer Docs > Versions for more information on version constraints supported by composer.
However, You may encounter conflicts with other dependencies like cakephp/debug_kit or cakephp/bake, which need to be solved manually, for example by downgrading or even temporarily removing them, as they may have been upgraded too and require a newer cakephp/cakephp version themselves!
I have installed beta package on test org. Now i have released another beta package.
But while installing it in test org it is now allowing to install.
So, Can we install Beta version on existing beta package?
Thanks in advance.
If it is an upgrade to an existing managed package you must first uninstall the current version.