We're having real problems with Hybrid and Umbraco 7.2.4.
Every time I do a build on the Framework, Umbraco 'upgrades' from 7.2.4 to 7.1.6 - presumably something to do with the dependencies stipulated in the framework.
I tried upgrading using Nuget and that was a total world of pain - pretty much everything stopped working, missing DLL's, invalid application sections, config sections giving errors, if it could get broken, it would.
We like the Framework, once you get it up and running it is really quick to build up a decent code base and the strongly typed models are a real benefit. But, and it's a BIG but, if it can't work with 7.2.x then this becomes a real show stopper for us and we would need to ditch the Framework completely.
Anyone else having these issues, and if so, what did you do to get round this downgrade/upgrade issue.
I've got a local version which is upgraded to Umbraco 7.2 and it works without problems. When I upgraded from NuGet I didn't overwrite any .config files. I manually checked the diffs between a clean Umbraco 7.1 and 7.2 install and added those changes to the .config files that are in the Hybrid Framework. I'm working on a new public version of the Hybrid Framework that will run on 7.2 or maybe even 7.3 if that's already out, but that's probably 2 or 3 months away.
Is that just the web.config file in the Framework then? That's the only .config file I have in the Framework directory that I can see, but if there are config files missing then that might be a reason for these issues.
My version is a copy from Maxi that I believe he downloaded from GitHub as the clean framework download.
Right, I think I know what's happening here. On the off chance, I deleted all the DLL's out of the Umbraco.Site folder, compiled the Framework and they all re-appeared.
Set the 1st two references in the Framework to not Copy Local, delete, recompile and these two referenced DLL's didn't copy over.
So when I build the Framework, it is overwriting the DLL's in the 7.4.2 version with the Framework's 7.1.6 DLLs and that's why I keep getting the upgrade message.
So I can either update your references in the Framework to 7.4.2, or not copy them over at compile time.
When you upgrade with NuGet also make sure you upgrade Umbraco.Core in the Umbraco.Extensions project. Otherwise it might happen that they get overridden again by older versions when you build.
We do seem to have issues when we upgrade through Nuget though as it seems to want to upgrade everything in site/sight and there are so many dependencies going on it causes all sorts of issues - I also made the mistake of going through the Nuget manager for the project and upgrading all the packages that were present. The latest version must be good - eh, no.
I guess the best way is to just upgrade the Umbraco CMS package - and probably even just the core binaries to be ultra safe.
However, mu downgrading upgrade seems to be sorted by not copying over the DLL's from the framework. Like all these things, blindingly obvious when you think about it.
just upgraded from 7.1.8 to 7.2.5, following the steps outlined above - here are my steps:
open hybrid framework in visual studio
use nuget on the .extensions project and just upgrade the
umbraco.core
use nuget on the .site project and upgrade the cms - nb, as stated, don't
overwrite the configs
download a new version of 7.1.8 and 7.2.5 and compare the web.config
and files under /config/, copying any differences over to your hybrid
versions in visual studio
update the umbracoConfigurationStatus in web.config to 7.2.5
update global.asax <%@ Application Codebehind="Global.asax.cs"
Inherits="Umbraco.Extensions.Utilities.Global" Language="C#" %> as
it was overwritten during the upgrade and will cause problems with
donut caching
build
run and enjoy!
Seems to work fine, not used it in anger yet, but will do shortly and if i find anything, i'll update
Umbraco v7.2 + Hybrid Framework
How can we make Hybrid Framework 7 compatible with Umbraco v7.2? Please can you advice.
Cheers,
Shaishav
Hello,
You should be able to just do a NuGet upgrade and everything should work. Only thing you need to look for is this: https://our.umbraco.org/projects/developer-tools/hybrid-framework-for-umbraco-v7/anything/60161-donut-output-caching#comment208234
Jeroen
We're having real problems with Hybrid and Umbraco 7.2.4.
Every time I do a build on the Framework, Umbraco 'upgrades' from 7.2.4 to 7.1.6 - presumably something to do with the dependencies stipulated in the framework.
I tried upgrading using Nuget and that was a total world of pain - pretty much everything stopped working, missing DLL's, invalid application sections, config sections giving errors, if it could get broken, it would.
We like the Framework, once you get it up and running it is really quick to build up a decent code base and the strongly typed models are a real benefit. But, and it's a BIG but, if it can't work with 7.2.x then this becomes a real show stopper for us and we would need to ditch the Framework completely.
Anyone else having these issues, and if so, what did you do to get round this downgrade/upgrade issue.
Cheers, Iain
Hello,
I've got a local version which is upgraded to Umbraco 7.2 and it works without problems. When I upgraded from NuGet I didn't overwrite any .config files. I manually checked the diffs between a clean Umbraco 7.1 and 7.2 install and added those changes to the .config files that are in the Hybrid Framework. I'm working on a new public version of the Hybrid Framework that will run on 7.2 or maybe even 7.3 if that's already out, but that's probably 2 or 3 months away.
Jeroen
Is that just the web.config file in the Framework then? That's the only .config file I have in the Framework directory that I can see, but if there are config files missing then that might be a reason for these issues.
My version is a copy from Maxi that I believe he downloaded from GitHub as the clean framework download.
Iain
The web.config is the file that probably has the most changes between 7.1 and 7.2, but also check all the files in the /config folder.
Jeroen
Right, I think I know what's happening here. On the off chance, I deleted all the DLL's out of the Umbraco.Site folder, compiled the Framework and they all re-appeared.
Set the 1st two references in the Framework to not Copy Local, delete, recompile and these two referenced DLL's didn't copy over.
So when I build the Framework, it is overwriting the DLL's in the 7.4.2 version with the Framework's 7.1.6 DLLs and that's why I keep getting the upgrade message.
So I can either update your references in the Framework to 7.4.2, or not copy them over at compile time.
Iain
When you upgrade with NuGet also make sure you upgrade Umbraco.Core in the Umbraco.Extensions project. Otherwise it might happen that they get overridden again by older versions when you build.
Jeroen
Good point Jeroen.
We do seem to have issues when we upgrade through Nuget though as it seems to want to upgrade everything in site/sight and there are so many dependencies going on it causes all sorts of issues - I also made the mistake of going through the Nuget manager for the project and upgrading all the packages that were present. The latest version must be good - eh, no.
I guess the best way is to just upgrade the Umbraco CMS package - and probably even just the core binaries to be ultra safe.
However, mu downgrading upgrade seems to be sorted by not copying over the DLL's from the framework. Like all these things, blindingly obvious when you think about it.
Cheers, Iain
hi
just upgraded from 7.1.8 to 7.2.5, following the steps outlined above - here are my steps:
Seems to work fine, not used it in anger yet, but will do shortly and if i find anything, i'll update
upgraded solution here: https://www.dropbox.com/s/hnvp86gxw8ukr3n/Hybrid.Framework.7.2.5.zip?dl=0
please if you use, add any issues/resolutions here as this is a great framework! kudos to jeroen!
is working on a reply...