Timeline for Is it required to build Compound Templates with Tridion 2013 DLL while upgrade?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 22, 2017 at 7:06 | history | edited | Bart Koopman | CC BY-SA 3.0 |
edited title
|
| Aug 22, 2017 at 7:06 | answer | added | Bart Koopman | timeline score: 1 | |
| Aug 22, 2017 at 6:55 | history | edited | Bart Koopman | CC BY-SA 3.0 |
deleted 1 character in body; edited tags
|
| Nov 26, 2014 at 12:43 | comment | added | robrtc | Pls answer your question yourself to close this question | |
| Sep 30, 2014 at 6:23 | comment | added | k951 | So this means that on content port from Tridion 2011 SP1 HR1 to Tridion 2013 SP1, Compound Templates will work normally (Because of backward compatibility). If we really want to know which all APIs are deprecated should build the solution with Tridion 2013 DLLs. | |
| Sep 29, 2014 at 18:36 | comment | added | Nuno Linhares♦ | It's a little thing called "backwards compatibility" and .NET policies. Even templates compiled against Tridion 2009 will work, though you may get some deprecation warnings. | |
| Sep 29, 2014 at 16:22 | history | tweeted | twitter.com/#!/StackTridion/status/516624180624646144 | ||
| Sep 29, 2014 at 14:29 | review | First posts | |||
| Sep 29, 2014 at 20:00 | |||||
| Sep 29, 2014 at 14:24 | history | asked | k951 | CC BY-SA 3.0 |