Take the 2-minute tour ×
Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It's 100% free, no registration required.

There are no Tridion 2013 SP1 files in the trunk yet of the DD4T codebase, but will the 2013 files work with SP1? Can we upgrade to from Tridion 2013 to Tridion 2013 SP1 without conflict?

share|improve this question
    
If Quirijn's method does work, let us know! –  Rob Stevenson-Leggett Dec 9 '13 at 18:13
    
I'm currently waiting for the Tridion 2013SP1 installation files from Tridion Customer Support. Will let you know when I find out. –  Thijs Dec 21 '13 at 15:31
add comment

4 Answers

up vote 5 down vote accepted

The 2013 provider will most likely break if it encounters a Tridion DLL with a different version.

There are two solutions:

share|improve this answer
add comment

The upgrade from 2011 sp1 to 2013 just meant rebuilding against the right Content Delivery DLLs and I would think the same applies for 2013 sp1.

It should only be the Provider DLL you need to change really. I would say try and create the provider and give back to the community!

share|improve this answer
    
We're actually thinking of upgrading from 2013 to 2013 SP1. There are no providers, yes, but I thought it might just work with the 2013 providers. –  Thijs Dec 9 '13 at 9:12
    
It might work, but as Quirjin said the problem is the version numbers of the Content Delivery DLLs have changed from 7.0 to 7.1 so .NET will not like the switch by default to protect from subtle bugs and mismatched methods. –  Rob Stevenson-Leggett Dec 9 '13 at 10:32
add comment

I hit a few compatibility issues with this this week and I've created a NuGet package which contains a version of the Tridion 2013 providers with updated references to the SP1 DLLs here:

http://nuget.org/packages/DD4T-Tridion-2013sp1/

For the time being, this will just replace the 2013 provider with updated references; however, I've requested write access to the DD4T codebase and will update the package with an independent SP1 assembly ASAP. This should do the trick in the meantime.

share|improve this answer
add comment

For the java version, there will be an updated provider jar next week if it doesn't simply work anyway.

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.