I have an existing ASP.NET MVC3 site that has been built with Sharp Architecture 1.9.6 and I'd like to upgrade to 2.0.4.
I've used NuGet to: Update-Package sharp-architecture. Obviously there are a number of compile issues...so I've been trying to update the references using the version history as a rough guide.
Unfortunately, it hasn't helped all that much since namespaces like SharpArch.Infrastructure seem to have disappeared somewhere between 2.0.0 --> 2.0.4 which is odd because I thought they used Semantic Versioning... but anyway...
I've been searching the interwebs for a guide on how to upgrade and I haven't come across anything helpful. Even reading through the sharp architecture blog hasn't helped me with this problem...
So does anyone know if there is a guide for how to upgrade to version 2.0.x? Surely it must be possible. Or is one expected to start a new site using Templify?
Related
im currently working on an update from laravel 4.1.24 to 5.6 The problem is i got nearly no experience with laravel. My question is now, how do i properly upgrade. Should i first upgrade to 4.2 and then to 5.0 and so on or would it be better to upgrade directly to 5.6 and how should i do this? I mean there are so many changes that i think i could miss something.
Also the project is just in a github repository, so it's hard to check if it's still working after an upgrade because i dont got the old modules. Or would it be enough to go on laravelshift. com and just upload it there to go from 4.1 to 4.2, 4.2 to 5.0 and so on.
Best regards!
The Laravel documentation contains a whole list of breaking changes that can help you to upgrade your application to a newer version. Laravel Shift is a service that checks and updates these changes in your project.
However, there is no way of being sure that your project will still work after these upgrades. Especially if you are using external modules its very risky.
If it is not required, I would not recommend upgrading from 4.1.x to 5.6 unless you have a lot of time on your hands. A solution could be to set up a completely new 5.6 project and add the project code file by file and test the implementations.
Start from here and follow instructions to upgrade it to 4.2. Then go through your packages and update their versions accordingly. When done use dropdown list in the top-right corner to select next version (5.0) and repeat it until you are at 5.6.
You definitely need to be able to run your code and test it somehow after each step because there will be problems. From 4.1 to 5.6 is a big leap and a lot of packages might have breaking changes etc. I only migrated as far as from 5.1 to 5.6 and it took me whole day to fix everything.
As for automated upgrade you can try it as well, but as I already mentioned you need to be able to test your work because all packages need to be updated as well.
I have some xamarin.forms 1.xx( I dont know which version) project on multiple platforms Android and iOS. And I've been asked to upgrade it to the maximum available right now version of xamarin.forms.
Therefore, I have 2 questions:
1) How to determine which version of forms I'm using right now (I'm working in Windows environment using Visual Studio 2015 ).
2) How to migrate/update to newest version of forms? (step by step, if it's possible). I have no idea how the result of that kind of operation supposed to look like, cuz I have never done anything like this before in my life. And what the best practices are?
What I've done is opened VS2015->Help->Xamarin release notes, however there was nothing about version of Forms I'm using. Also, I went to the official xamarin website and there was no guide how to do that. I also tried to look at the release notes the last Forms update and trying to find and fix differences, but my project is so big and I thought that this way doesn't seems right.
I'll answer first the What are the best practice regarding upgrading a Xamarin.Forms application? first and then address your other concerns.
I recently upgraded from 1.5.1 to 2.3.2, and from my experience, this is the steps to go through:
Decide which version you will upgrade from and to.
Read the change logs for all stabled releases between these two versions and look for breaking changes/bugfixes. You can find the release notes on Xamarin's website or on NuGet's website too.
Check regularly for new releases on the Xamarin.Forms forum and check if any reported issues may affect you. Every time Xamarin makes a release, there is a thread full of comments from other developers that may have encountered issues you might be interested in.
Using your favorite versioning software, make sure that all local changes are commited or stashed and create a new branch for your Xamarin.Forms upgrade (you don't know how long the upgrade will take and you still want to be able to send patches during the process)
Upgrade: Read the Important notes at Xamarin.Forms 2.3.2 release notes, especially the When upgrading Xamarin.Forms take care not to simply "update all" as ... part. Remember to upgrade on your PCL project, on your iOS project and on your Android project.
Test your whole app on as many devices as possible and for the longest possible period before you merge your branch back into your development/master/Main branch and address the potential incompatibility issues that may have been created in your development/master/Main simultaneously.
Step 3 is very important as it will allow you to reset back to your starting point and restart if you should fail to upgrade for whatever reason.
Xamarin.Forms is moving fast so it's important that you always keep an eye on what's going on even if you don't upgrade.
Which version am I using right now?
You can check that in the NuGet package interface or in the packages.json file in your project.
I have been tasked with fixing a bug found in a legacy app written in version 2.4.0 or 2.6.0 of STS.
After spending the better part of 2 days trying to port it to 3.6.2 without success I need to get my hands on either of these older releases to see if this even works or if there is something wrong with the app code base. I have spent the better part of an hour searching STS Spring for previous versions but can't find anything on the site. Where are previous versions of STS or why have they been stashed away?
OS Target: Window 7 - 64 bit
Thanks
Having a look at this post and the filename of the current version, you come up with: http://download.springsource.com/release/STS/2.6.0.SR1/dist/e3.6/springsource-tool-suite-2.6.0.SR1-e3.6.2-win32-x86_64.zip
Very strange that they are not linking the old versions even though they are still available.
I'm new to CI. Anyone could help to the latest version of CI. most of the Tutorial is for last version and it didn't work for the latest version. please help.
You can still get started using what's availabe for 1.7, if you pay attention to how file structure changed between the two versions (ie the System and Application directories are now separate). To that, many of the tuts you'll find are applicable - bearing in mind that the paths may differ, and you'll want to verify that the functions are still supported in 2.0 by use of the User's Guide).
If you walked through the tut in your link, using the Models, Views, Controllers directories inside Application, you'd get a "Hello World" page.
The User's Guide is a great tool, as are the Community Forums.
Best of luck to you.
I recently migrated a site using CodeIgniter from 1.7 to 2.0. - I found the following link to be very useful:
http://philsturgeon.co.uk/news/2010/05/upgrading-to-codeigniter-2.0
i want to port my application to CodeIgniter but i am wondering whether i should use their v2.0 or v1.72 (then when they release 2.0, upgrade it).
i have never used a framework before so i don't exactly know what implies when upgrading a framework: what does it mean practically - i just move the folders and it will work? or do i have to change a lot of settings, file structure etc? could someone enlighten me about the upgrade process.
and what would you use: v.1.72 or v2.0?
if i'm using the latest version, is there a good documentation for it somewhere so you can read about how to use the new features: packages, drivers and so on.
thanks
You can read about some of the changes in 2.0 here.
I would image the upgrade process should be straightforward as long as you do not use any features that are different/removed such as plugins. Just take your models, controllers, etc and drop them into the 2.0 framework. Then regression test you whole app, fixing any problems as you see them...
If you are selling this app or making something mission critical then of course v1.7.2 is the best choice. That said I have PyroCMS running on v2.0 and since some of my bug-fixes were merged it seems stable enough.
One should consider time frames for deployment:
If it is one week, then stick to v1.7.2
If it is three months, go with v2
Assuming three months is approximately to time for a release to stabilise?