When I did an upgrade from 7.2 to 8.1 earlier this year, I followed these steps:
Setup a new instance of Sitecore 8.1 and configure it according to the documentation.
Get my settings/layouts into some sort of source control (using Unicorn or TDS)
Apply those settings/layouts to my new instance
Compile the existing code against the new version of Sitecore, ...
I normally try to split DB upgrading from code upgrading.
This allows me to run the DB upgrade process of vanilla Sitecore instances where any customisations won't interfere with the db upgrade process.
I then upgrade the code as per the SC upgrade guides (and yes this means going through each one). This can take some time because the config changes a lot, ...
The answer to this depends on the context of your project. Sitecore's recommendations are to make incremental upgrades for every version and updates as well since your current to the latest you are trying to get upgraded to. This does require a lot of work specially when it's a big jump from 6.5 to 8.2. As already answered here if you are making manual ...
In my experience, when you plan major changes in your solution, the worst thing you can do is apply all of them at once. When you inevitably run into problems, you won't know which of the changes caused them; that will make debugging and fixing so much harder.
Generally, the most reliable approach is to split your changes into as many small steps as ...
No, it does not.
Also see here: https://dev.sitecore.net/Downloads/Web_Forms_For_Marketers.aspx
Note! Web Forms For Marketers was deprecated with the release of Sitecore XP 9.1
9.0.2 is the last release where WFFM can be used.
Pre Sitecore 8.1 (which splits out the Sitecore node into /App_Config/Sitecore.config) - I generally create my own Sitecore.config and patch that into the web.config in the same way as the connection strings is done.
Then yes, I just have the resulting web.config from my Sitecore installation in the web project. With debug transforms for local development.
As the product owner, let me confirm.
In version 1.x --> 3.2 the Email reporting stack was built on a foundation that was inconsistent, inaccurate and not able to scale with the future of Sitecore. The reporting UI was poor and did not meet the expectations of nearly any of our customers.
This means we had to take huge steps to make our customers happy in ...
Well, now it's working all of a sudden after having spent most of the day on this...
What I've done recently is run the Clean up databases from the Control Panel and rebuild the link database and the search indexes.
So, if you run into this issue try that.
The generated sprite files are located here:
To answer your question, really, I feel it's prudent to walk through
the deployment steps and call out where places that might be gotchas.
I'll finish with a summary of what I would do.
Sitecore 7.5 - 8.0 Initial (141212)
The first step that you'll want to do is upgrade to the 8.0 Initial release. You can find the Upgrade Guide here. During this ...
One might think that there is already a similar question
on this matter. However, your exact question is a bit different.
An Upgrade Approach
As far as unwiring the existing DI containers (and updating Sitecore), I would start with trying to eliminate upgrade complications first.
1. Start with just removing your old DI completely.
While this may ...
This seems to be related to the .net version you are targetting on your projects. Sitecore 9 requires .Net 4.6.2 or 4.7. It seems like one or some of your projects are using 4.5.2.
Compatibility table reference: https://kb.sitecore.net/articles/087164
By far the most common solution to this is to use Web.config transforms built into Visual Studio and MSBUILD. The following MSDN articles should give a good jumping point:
You may also want to consider SlowCheetah for ...
The Sitecore 8.2 Release Notes provide a wealth of information around the changes that come along with 8.2. I would definitely pay attention to the breaking changes section. Largely, the 8.2 Version of Sitecore was very Developer focused and not as much has changed on the marketing side.
Specifically though, the biggest, noticeable, differences in 8.2 ...
There definitely are reserved field names. Any field on the Standard Template should not be used. I would also recommend you use an Id where possible.
You can see the use of this pattern in the Sitecore.Kernel.dll where fields found in the FieldIDs class are used when accessing standard Sitecore fields. The use of the Id will of course be fast as well as ...
Having done a fair few of such upgrades in the past, I'll chip in with my own view as well.
And it will probably not be entirely without controversy.
Scrap and rebuild
My advise to you would be: scrap it. And rebuild. And since you indicate you've already received a "very high" quote for the work, my guess would be that this is more or less what the ...
The issue you have is that one or more of your profiles are corrupt. Either by renaming or deleting. Everything internal to Sitecore profiling works off of names, not profile keys item or pattern card item IDs.
The way to solve this is to clean up the names/items in the database. To do this navigate to https://[YOUR_SITE]/sitecore/admin/DbCleanup.aspx, ...
The shard manager also keeps connection configuration in the [__ShardManagement].[ShardsGlobal] table of the ShardMapManager database. There is a ServerName, Port and DatabasName in there, so make sure these also point to the correct SQL server.
You can find the downloads for the migration/upgrade tools on the Sitecore 9 release page: Sitecore 9.0 Initial Release Downloads
Since you are on 8.2, you can use the 'upgrade' package there.
Specifically for the xDB data, you'll want to look at the xDB data migration tool
If you are on an older version of Sitecore, the express migration tool 3.0 has ...
The reason you are getting No parameterless constructor error is because Sitecore cannot create an instance of your controller that takes parameters. Without dependency injection working correctly, Sitecore is looking for a controller that takes not inputs like this:
public ActionResult MyController()
What you do have is one that takes ...
The system index from <search> node was marked Obsolete in config (SC8.1.3) and completely removed in Sitecore 8.2 Initial Release.
<!-- Obsolete: the API that uses this section is obsolete. Please, use Sitecore.ContentSearch to configure your indexes. -->
<configuration type="Sitecore.Search.SearchConfiguration, Sitecore....
Your idea is similar to the way that I used to perform upgrades before TDS. The below is the strategy that I used to use, which I call the "Hybrid-Clean Upgrade Strategy":
Hybrid-Clean Upgrade Strategy
Identify your upgrade path (all the versions that you will need to "pass through" as you iteratively upgrade to your target version) and set your current ...
Pipeline Sitecore.Pipelines.Loader.ShowHistory is no longer used.
Check your web.config (or sitecore.config) in App_Config and remove reference to this pipeline.
But, if you have issue with this pipeline, most probably you have more corrupted configs in your solution. You may want to compare them with the clean Sitecore 8.2 configs.
In short it's not easy to do this as version 6 is pretty old (nearly 9 years old to be exact!).
Sitecore have released a tool to upgrade from 6.6 or 7.2 to 8.2 but it will not do everything for you and it depends on the customisation and how they have been done as to how much manual work there will be to do: https://dev.sitecore.net/Downloads/...
You have redirect user to "/sitecore" instead. You will also need to create the cookie by calling createticket function. Here's a snippet of what should be called after AuthenticationManager.Login.
string ticket = Sitecore.Web.Authentication.TicketManager.CreateTicket(userName, @"/sitecore/shell");
HttpContext current =...
Some of the more "business focused" changes in Sitecore 8.2 that clients would be interested in also include:
Express Migration tool from Sitecore 7.2 to 8.2
Publishing Service making publishing faster and more robust
Support for Precompiled views making restarts faster after a deployment
Numerous improvements in the Experience Editor
This is a typo in the upgrade guide. It should state Sitecore 8.2 rev. 171121 (Update-6) Update Package.
In more recent versions of the upgrade process, Sitecore has changed the way they allow the update process to take place. If you take a look at the .update package you will notice it is much larger than previously (Sitecore 8.2 rev. 171121.update is ...
I have had that config after an upgrade as well - and you should have a Sitecore.Upgrade82 dll in your bin folder that comes with it.
So if you delete the config, you can delete that dll as well.
But can you delete it? Well, it depends I think. I did and everything was still working but I also used a clean config set from a 9 setup. I decompiled the ...
After reviewing Sitecore's upgrade documentation (All 8+ versions are listed here: https://dev.sitecore.net/Downloads/Sitecore_Experience_Platform.aspx. Each page has a link to it's Upgrade Guide which indicates pre-requisites for installation) the upgrades you would need to perform to get to Sitecore 8.1 Update 3 would be:
Upgrade to Sitecore 8.0 Initial ...