We have Live Site running with Umbraco 3.0 version. Now, we want to use latest Umbraco V4.7. We need to know how it is possible? Is there any Open Source OR Free Tool which can support this?
Upgrade to each major version in succession. First, upgrade from 3.0 to 4.0, then 4.0 to 4.5.2, then to 4.7.
If you need help I have a blog post recording the process I have done from 4.0 to 4.7.
Notes and Experiences Upgrading Umbraco 4.0.x to 4.6.1 and 4.7.0
Create a package of your current site, this can be done with the help of Developer section -> packages -> create package in umbraco.
Then in ver4.7 install that package again in a blank site, your prevoius site should be up.
Related
I have downloaded and installed VS2019 Community v16.6.0
I have downloaded and installed .NET Core 3.1 (v3.1.4) with SDK version v3.1.300
.NET Core 3.1 is not available as an option for a target framework in Visual Studio. Am I missing something here?
I've followed several suggestions in other similar questions of enabling preview SDKs (which shouldn't apply, because 3.1 is not in preview) with no success.
Images Attached
v16.6.1 of VS2019 just dropped today. Fixed the issue.
What is the difference between umbraco and vanila umbraco.
i'm currently using umbraco 6.2.1 version in my website.
Any special procedure available for upgrading this version to Vanila umbraco version.
Vanilla Umbraco means a fresh clean installation of Umbraco, without any customization.
Vanilla is a general term used for software, see also on wiki
Related to upgrading, one approach is to do a new installation of Umbraco (we can called it a vanilla installation) and then deploy your code, and migrate the content. Instead of the General Umbraco upgrade instructions.
I'd say that there is no running website with a vanilla Umbraco install. Umbraco is not a typical CMS. You are customizing it as soon as you start setting up your site in it. This is partly due to a choice on the Umbraco HQ team's decision to store their settings in the same files where you change settings by using Umbraco, requiring you to merge certain files during the upgrade.
As for upgrading, I'll warn you, there are a few ways to install Umbraco (Web PI, Nuget, Zip file), and if you upgrade in a way different than you installed, it can be hell. Step one, back up your site (front-end file-system files and db)! If you did not install Umbraco via Nuget (in Visual Studio), do not upgrade via Nuget. You will regret it.
Umbraco upgrades are a problem.
If the versions are minor running the update-package umbracocms nuget might work, but it often leaves the project mismatching version assemblies elsewhere.
Upgrading Umbraco is a bit of a minefield. Soz
Umbraco is now at version 11 and have moved their code base from the .NET framework into .NET core. Newer version is offering so much more, block-list, block-grid, inline editing, so many new and improved property editors. Editing experience and working with the CMS has changed so much since version 6.
Vanilla Umbraco would a term for a non-configured, fresh install.
You can find out everything you need to know about Umbraco on their documentation pages.
https://docs.umbraco.com/getting-started
Umbraco is a free open source project so there is no cost if you want to roll your sleeves, dig in and move over to the newest version. There are some paid offerings as well that would give support if you needed it.
Now that they have moved away from the .NET framework and moved their code base over to .NET Core there is no longer a direct path to upgrade from version 8 and earlier to the most recent version 11.
I would recommend you set up a fresh install, configure and customize as desired and then move any relevant content over to your new site.
There are many articles out there detailing how others moved over to the newer version.
Good article here on how they upgraded from version 7 to the newer version 11.
https://skrift.io/issues/how-i-upgraded-my-umbraco-v7-project-to-umbraco-v11/
Worth the read if your planning on going down that path.
Good luck.
I have an umbraco WebForms projects built on 4.11.10 that we need to upgrade to 7.3.8.
We have tools such as RedGate Data Compare and RedGate Structure Compare, but without firsthand knowledge of the new structure and how that has affected the way that data is stored we're finding it impossible to upgrade the database.
Does anyone know of a SQL script or tool that will upgrade just the database to the new format?
Thanks in advance for your time.
dotdev
Recent changes in 7.3 greatly improved the experience (and success) of upgrading from older versions.
Incredible engineering by the Umbraco core team, the new installer
just upgraded a 4,5 year old v4.7.1 db to v7.3 flawlessly #h5yr
https://twitter.com/umbraco/status/643721449295974401
This blog post contains some more details on performing an upgrade from 4.7.1 to 7.3.
I recently upgraded to Resharper 8.1 and VS 2013
Before I could ctrl+click on a View to jump to it, but this no longer works. Is there a feature I need to enable to get it back?
PartialView("_MainMenu", viewModel);
Go to Resharper->Manage Extensions and click the Online tab. Then search for Resharper.ExternalAnnotations, and install the package it comes up with.
Finally go to Visual Studio Tools->Options and go to the Resharper->General options page. Click Suspend Now followed by Resume to restart Resharper.
About workaround for previous versions of ReSharper:
You can download package with annotations https://resharper-plugins.jetbrains.com/api/v2/package/ReSharper.ExternalAnnotations/8.1.1000.431 and unpack content of ReSharper\vAny\annotations\ folder to C:\Program Files (x86)\JetBrains\ReSharper\vX.Y\Bin\ExternalAnnotations, where X.Y is your version of ReSharper.
Better first to clean target folder up to avoid annotations duplicates.
ReSharper 8.2.1 (8.2.1000.4556) doesn't support MVC 5.2
EAP for 8.2 is closed
Bug registered
UPDATE:
FIXED: reply about fix from the Resharper team
You need to restart the VS and you will get notification about Update or run it manually from the Resharper => Extension Manager => Updates => Resharper.ExternalAnnotations (like in the Samuel answer)
There still seems to be an issue with ReSharper and navigating to MVC Views or having the QuickFix (Alt+Enter) functionality available on them in the latest (as of this writing) version of ReSharper - v8.2.3000.5176.
My MVC version is 5.2. My ReSharper version is 8.2.3000.5176. When I installed this it seemed to install the ExternalAnnotations that come bundled with the update, also versioned at the same version number.
I can fix the issue by uninstalling the ExternalAnnotations (version 8.2.3000.5176) and re-installing the latest version offered from the ReSharper Gallery (which is version 8.2.2001.1). After a Visual Studio restart, my MVC quick-fixes and View navigation is back.
Strangely, I also get prompted by ReSharper that extension updates are available, and it wants to upgrade my ExternalAnnotations to version 8.2.3000.5176. If I do this (and restart VS) everything breaks again. Downgrading back to version 8.2.2001.1 (and a VS restart) will, however, fix it again.
A number of other people are also reporting this issue on JetBrain's ReSharper blog post that announced ReSharper 8.2.3
So, if you're using MVC 5.2.x and ReSharper 8.2.3, try to downgrade the version of the ExternalAnnotations that you're using and see if that solves the issue.
UPDATE (5th November 2014):
There is now a new version of the ReSharper External Annotations available from the JetBrains "ReSharper Gallery". This new version is v8.2.3001 and I can confirm that once installed, this new version fixes the problem for me!
ReSharper 8.1 just doesn't support MVC 5.1
Latest EAP builds of ReSharper 8.1.1 do.
There should be no problems with running your ctrl+click and no additional configuration (enabling/disabling anything) should be needed. So it is most probably some bug.
Your situation might be connected with the following known issue reported here. It is connected with IntelliSense, not with Resharper directly, but they are both related to problems with navigating in Razor engine when having VS 2013 and newest ASP.NET MVC.
Below the summary of the issue description and some workaround to fix it:
MVC 5.1 Tooling Support and Razor IntelliSense are Still Broken Even
After Installing VS2013 Update 1 RC
Known issue:
If a VS2013 user installed “Microsoft ASP.NET and Web Tools 2013.1 for
Visual Studio 2013” before they install VS2013 Update 1 RC, they won’t
be able to get MVC 5.1 tooling support that comes with VS2013 Update 1
RC.
Symptom:
MVC 5.1 tooling support and Razor IntelliSense are still broken even
after installing VS2013 Update 1 RC.
Workaround:
From "Add/Remove Program", uninstall "Microsoft ASP.NET and Web Tools
2013.1 for Visual Studio 2013" Repair VS2013 RTM Install VS2013 update 1 RC if you have not yet installed it. If you have already installed
this, you don’t need to reinstall or repair it. From Web PI, reinstall
Microsoft ASP.NET and Web Tools 2013.1 for Visual Studio 2013 or
repair Azure SDK 2.2.
try ctrl+B while cursor some where on the View()
Can any one teach/guide me the best approach for upgradation of spree 1.1 to 2.1 version If any one have idea?
Actually I am looking to upgrade spree version from 1.1 to 2.1 where I am getting the more dependency errors why because I have used more spree extentions which are supportable to spree 1.1.
I am looking for compatible version of these extensions with spree 2.1.
I don't find any below extentions compatible versions with Spree 2.1.
spree_essentials
spree_essentials_blog
spree_essentials_cms
spree_social
spree_address_book
As per my review, Its big deal to upgrade spree along with above extensions..
Please any one share me your idea on it If you thought/find any compatible version of above extensions with latest spree 2.1 ver.
I am eagerly waiting for your reply/help.
Thanks In Advance.
One important thing is to upgrade to each major/minor release along the way. In your case you'll need to go:
1.1 -> 1.2 -> 1.3 -> 2.0 -> 2.1
You can upgrade to the latest patch release for each minor version, or upgrade to the 'x-x-stable branch on Spree's github (for example 1-2-stable).
Then you're correct that you're going to have to deal with all of the customizations that you've made. 2.1 is a very new release. It also makes a significant change moving from Rails 3.2.x to Rails 4.x. You'll need to follow a Rails 3->4 migration guide for your application in order to get your application working in Rails 4 (outside of Spree).
Because Spree 2.1 is so new, and you have to upgrade each release along the way, I'd probably recommend that you stop at 2.0 for now. You're more likely to find extensions that work with 2.0. Remember to check Github forks for people who have already upgraded the support Spree version of those extensions.