I want to start a new Laravel project, this project is a platform which may be we should develop and maintain for several years.
Now, I'm wondered to choose the correct Laravel version.
In the Laravel Support Policy page, Laravel said the 5.5 version will support until Aug 2020, but the 5.7 version will support until Sep 2019!
Which version I should choose for the new project?
Should I choose the latest version or long-term support version?
I would go with the latest version.
Laravel is a robust framework, but its LTS is kind of a joke.
Just as an example, if you go with any laravel version below 5.7, you can't have a working version of Socialite out of the box, due to the latest Google changes.
This is just an example as Socialite is not Laravel and only Laravel is LTS, it's still part of the ecosystem though.
So choose wisely as the migration process is not always very easy when you have the project in production.
Related
As Magento's new version 2.4.4 is about to release. all developers are looking for the upgrading process from 2.4.3 to 2.4.4. what are the areas which we need to look into as developers?
what are the major changes happening? what if we are using third party applications and integrations in our Magento instance
The official upgrade guide can be found: https://experienceleague.adobe.com/docs/commerce-operations/upgrade-guide/implementation/perform-upgrade.html
What is the best way to upgrade Abp Framework 4.1.0 to latest version 6.3.1? And does it upgrades EF core version and .Net core version?
Steps
Update the .net framework to the latest version
You can update the nuget packages related to abp to the latest version
Add a migration (update the database), this because there are changes in the properties of the framework entities
The UI theme was also changed to AdminLte, although this should not be a problem.
Lucky!!!
I've recently taken a client with an existing app using MvvmCross and the Community.Plugins.Sqlite. It looks like the old 3.1.1 version is all that is in nuget, which supports the classic ios api. Is there a version anywhere for the unified api?
Wally
The Community code supports iOS unified but you have to download the latest source and compile. We are debating whether or not to just swap out Sqlite-net for one of the PCL options.
How do i uninstall an already existing version of phonegap(1.3,1.8) because i want to install the new 2.0 and it does'nt get installed without uninstalling older versions. The folder structure of my older version 1.8 does'nt have uninstall option.
Any suggestions are welcome.Thanks.
Cordova 2.0 onwards doesn't really have an 'installer' so you should be perfectly fine to leave your 1.3 if you like.
They only recommend uninstalling old versions if you are not going to use it so that the project template is removed from XCode. If you don't care about that you can leave the old version.
Just follow the upgrade steps from http://docs.phonegap.com/en/2.1.0/guide_upgrading_index.md.html#Upgrading%20Guides to start using 2.1 (which is now out and you should use)
Currently the newest version of Azure SDK is 1.5, but I'm using 1.4 and don't want to waste time upgrading right now.
Will I face any problems deploying a package built against version 1.4 onto live cloud? How long (approximately) can I continue building against version 1.4?
Other than the pre-PDC CTP SDK, all RTM versions of the SDK are supported and continue to be supported. Before I left MSFT, there were customers still on v1.0 and it had literally been > year. I can't find any official documentation on SDK support windows, but we used to say the support window was very long and that you would be given a lot of warning if things were going to be deprecated (like CTP SDK versions).