IS There a way to define a Transformation not in the Portal

Craig Hazard asked on September 9, 2014 06:11

I was wondering if it is possible to define transformations in Visual Studio? I know i can modify or create new Transformations for Documents in Kentico Portal, but for source control reasons storing everything in the database makes me a bit uncomfortable.

Is this possible, or am I stuck defining my transformations through the Portal.

Correct Answer

Brenden Kehren answered on September 9, 2014 06:51

Have you checked out the developer documentation?

Once you get used to Kentico you won't have a need to store the transformations within the file system. Kentico offers version control for objects and content. So if you modify a transformation, layout, user, etc. that version is stored for you similar to using version control.

1 votesVote for this answer Unmark Correct answer

Recent Answers

Bryan Drenner answered on September 9, 2014 18:31

Craig, I've struggled with this same problem, myself. I mean, seriously? Storing views in the database?

Actually I just stumbled upon a potential solution: Deployment Mode. You can have Kentico store those views, so-called "virtual objects", in the file system. Check out the documentation: https://docs.kentico.com/display/K81/Deployment+mode+for+virtual+objects

0 votesVote for this answer Mark as a Correct answer

Bryan Drenner answered on September 9, 2014 18:50

Hah! I just realized I posted the same link as Brenden.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on September 9, 2014 21:35

Some views and queries and such are stored in the database simply so Kentico can do what it needs to resolve macros in that text. If you're concerned with versions and losing code or content, take more frequent backups of your database.

Using the link I provided is more of a temporary, development solution. IMHO, you won't want those checked out when you deploy the site live and I believe Kentico states/suggests to check them in prior to publishing as well. Remember is a CMS, not a bunch of aspx or ascx pages you're creating. It's supposed to be dynamic.

0 votesVote for this answer Mark as a Correct answer