I am on the latest version of magento2 CE (currently 2.3.3), I use composer for upgrades
composer outdated
shows me a lot of outdated packages.
How to easily upgrade/update these outdated packages to the latest versions?
Tried require them one by one, which is a lot of hassle, also because inter dependencies
another sub question is, does composer look at which packages are compatible with magento 2.3.3 when it tells which packages are outdated? perhaps i can better stay with the packages as bundled with the default magento 2.3.3 project composer.conf as they might be mostly tested with and compatible.
Related
I'm upgrading Ruby on my Gitlab Server from 2.7.2 to 2.7.4. But I'm not able to see the upgraded version on the Admin Area Dashboard. It still shows the earlier version and when I do a ruby gem list it tells that all the gems have not been got according to the new package. I'm upgrading ruby without any package manager, i.e. from the source. Kindly help me.
so, I wanted to freshly reinstall some Microsoft Servicefabric packages and for that I uninstalled all related packages from my given projects.
When trying to reinstall them, I run into the following issue:
When trying to install said package, this happens:
It seems like I have run into some kind of circular dependency here.
My project is currently clean of any any Service Fabric packages, so I am very unclear why Nuget is trying to RESTORE instead of REINSTALLING the packages.
Also, I am quite unsure how I could resolve this right now.
Can someone guide me?
The error message complains about the incompatibility between Autofac.ServiceFabric 2.2.0 version and Microsoft.ServiceFabric.Services.Remoting 3.4.641 version package.
Assuming your asp.net core project targets .net core 2.2.0, you can try to add reference to corresponding Microsoft.ServiceFabric.Services.Remoting 3.3.644 version instead of the incompatible 3.4.641 version. Then the Nu1608 and Nu1107 error would go away.
(The Autofac.ServiceFabric 2.2.0 and Microsoft.ServiceFabric.Services.Remoting 3.3.644 were both released in 4 months ago)
My Magento install is not showing any available upgrades for Community Extensions.
When I run mage from the command line I receive No updates available (Magento is up to date). It does show the installed modules so no problem with the packages.xml.
To test I restored an older version and re-ran the upgrade, this shows me all of the current Magento core upgrades. However nothing for the extensions (which mirrors what I see with the live install)
If I log into Magento Connect it shows all my installed extensions and their versions but nothing in the column that shows the available version.
n98-magerun :sys:check shows no problems
I have googled and tried everything I can think of and can't figure it out
We are running CentOS 7.4
Any pointers would be very helpful :)
Thanks
Darren
I have my project in visual studio and i am using installshield as my windows installer. When I am installing new updated version of my application it will shows
Another version of this product is automatically installed like this...
How can I install new version by overwriting my old version?
Is there any way to configure in installshield or give me any other way
?
The error that you're getting is because the ProductCode has not been changed. This code is what makes your product/installer unique. Generally to author the upgrade you'll need to change this code and make sure the UpgradeCode is the same so that it recognizes what is already installed.
Authoring upgrades is a much wider topic and far too much information then can be covered here. I would suggest this page for learning about Windows installer upgrading.
Every upgraded version of install should have a different ProductCode. UpgradeCode is what tells the install package that this product has been installed. If ProductCode is also the same, install assumes you are installing the same product again. ProductCode needs to be different for each of the updated packages.
Under The Upgrade Paths, create a new path. Leave the min version blank (unless you need it), include min version yes, Max version should be set to the version You are installing now. Include max version to yes.
Each time you are installing an update, Increase the Product version(If u want to change) in the General Information section. Click on a new Product Code in the General Information Section Do not change the upgrade code.
Go back to the upgrade path, and set the Max version to the same version you are deploying now.
And make sure the Upgrade code in the "General Information" and "Upgrade path" are same.
This process uninstalls previous version, and installs the latest. No duplicates in add/remove programs.
If any doubt on this, comment your question...
When you do gem install someGem, does it install it in your system so it's available for all your projects, or does it only install it for the project that's associated with the folder you're currently in?
This depends on how it is set up. Normally it would be available for all projects but it can be set up as in this tutorial http://janveldeman.wordpress.com/2008/04/14/project-specific-rubygems/ (From 2008 so might require a big of playing to get working with newer versions) to be specific to individual projects.