Codify

A Powerful .NET
Code Generator

Frequently Asked Questions

What programming languages are supported by Codify?

Codify supports embedded code generation for C#, VB.NET, and Visual C++. Any language is supported when Codify is used outside of Visual Studio .NET with FileBuilders.

When authoring templates Codify supports two distinct types of rendering scripts: CodifyScript and XSLT. CodifyScript is an ASP-like scripting language that works similarly to C#.

My team has a set of Codify templates that we all put on a network share. How do I make Codify use the template on the network, instead of local copies?

There is a way to share a template file between projects. The CodeBuilder XML contains a TemplateMoniker element which instruct Codify on which template to use. All your CodeBuilders will have a project reference that looks something like this:

project:MyTemplate.cbt

You can also use a file reference:

filespec:C:\Templates\MyTemplate.cbt

The filespec reference will tell Codify to look for the template on the file system, not in the project.

I am trying to activate my install of Codify, but it keeps telling me my Order ID or email is incorrect. What am I doing wrong?

A common mistake when trying to activate your Codify installation is not using the correct email address. The Codify licensing system needs the Order ID and the email address of the person that ordered/purchased Codify. If someone else in your company bought the product and received the "order receipt" then you have to use their email address. We can help you find your order details if they are lost by contacting team.codify@workstate.com.

Why don't the Template Editor build error line numbers match my rendering script line numbers?

The build error line numbers are actually the line numbers of the compiled "rendering class" for Codify. When you double click on the error, it will take you to the exactly line of the compiled rendering class. This way you can see the exact cause of the compiler error, and then update the rendering script appropriately.

What does "The CodeBuilder named '[CodeBuilder Name]' starting on line # was not closed." mean?

When you run the CodeBuilders in your project files, the Codify parser looks for a beginning and an ending Region directive. The End Region direction should look like:

C# -> #endregion // [CodeBuilder]

VB.NET -> #End Region ' [CodeBuilder]

If the comment is removed from the end region, or the end region is missing, you will get this error. You can eliminate this error my ensuring that the "End Region" directives look like the above items.