Comments on: Clarion T4 template walk-through http://clarionsharp.com/blog/2010/07/clarion-t4-template-walk-through/ Simply the fastest tool available for creating custom database applications! Fri, 20 Jan 2012 19:27:17 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Angel Bermudez http://clarionsharp.com/blog/2010/07/clarion-t4-template-walk-through/comment-page-1/#comment-508 Angel Bermudez Sat, 17 Jul 2010 01:13:25 +0000 http://clarionsharp.com/blog/?p=768#comment-508 This information is great and exciting, however, you should consider blogging more often. This information is great and exciting, however, you should consider blogging more often.

]]> By: Peter Donovan http://clarionsharp.com/blog/2010/07/clarion-t4-template-walk-through/comment-page-1/#comment-504 Peter Donovan Tue, 13 Jul 2010 05:31:51 +0000 http://clarionsharp.com/blog/?p=768#comment-504 Will my existing Clarion code (currently in Clarion 6) be able to be ported to Clarion .NET? Have a large existing application and need to find a way to get it to the Clarion .NET without having to re-write it. Cam you suggest any way at all of this being able to be done? Will my existing Clarion code (currently in Clarion 6) be able to be ported to Clarion .NET? Have a large existing application and need to find a way to get it to the Clarion .NET without having to re-write it.

Cam you suggest any way at all of this being able to be done?

]]> By: Diego Borojovich http://clarionsharp.com/blog/2010/07/clarion-t4-template-walk-through/comment-page-1/#comment-502 Diego Borojovich Wed, 07 Jul 2010 21:52:18 +0000 http://clarionsharp.com/blog/?p=768#comment-502 Hi Graham, Yes, you can create your own compiled symbols. We will ship an example that it is actually used in the wizard. There are some public interfaces to that can be used in your own code to read the DCT & App properties. As an example, the application wizard use an external assembly to create the Project and app and instead of just generate the text files by hand it use that assembly classes to create an object that represent the project and when finish write that project down to disk with out syntactic errors (to many ) Hi Graham,
Yes, you can create your own compiled symbols.
We will ship an example that it is actually used in the wizard.
There are some public interfaces to that can be used in your own code to read the DCT & App properties.
As an example, the application wizard use an external assembly to create the Project and app and instead of just generate the text files by hand it use that assembly classes to create an object that represent the project and when finish write that project down to disk with out syntactic errors (to many )

]]> By: Diego Borojovich http://clarionsharp.com/blog/2010/07/clarion-t4-template-walk-through/comment-page-1/#comment-501 Diego Borojovich Wed, 07 Jul 2010 21:47:44 +0000 http://clarionsharp.com/blog/?p=768#comment-501 Hi Russ, yes, that is exactly what it means. You can create you own assembly (DLL) with your own Type Editor and declare a property of that type and it will show in the template and you will be able to call it. Also you can create you own functionality in a separated assembly and call it. There is one special directory for external assemblies to be found. The local symbols are local, but you can pass it as parameters. Hi Russ, yes, that is exactly what it means.
You can create you own assembly (DLL) with your own Type Editor and declare a property of that type and it will show in the template and you will be able to call it.
Also you can create you own functionality in a separated assembly and call it.
There is one special directory for external assemblies to be found.
The local symbols are local, but you can pass it as parameters.

]]> By: Graham Dawson http://clarionsharp.com/blog/2010/07/clarion-t4-template-walk-through/comment-page-1/#comment-500 Graham Dawson Wed, 07 Jul 2010 13:49:09 +0000 http://clarionsharp.com/blog/?p=768#comment-500 That looks great - many thanks for posting. Lots of questions but I'll just post one. <#@ assembly and <#@ import namespace should allow us to use our own assemblies within a template correct? But will those templates be able to 'see' the built-in template symbols, and symbols declared in a 'helper block' within the current template. Graham That looks great – many thanks for posting.

Lots of questions but I’ll just post one.
<#@ assembly and
<#@ import namespace
should allow us to use our own assemblies within a template correct?

But will those templates be able to ‘see’ the built-in template symbols, and symbols declared in a ‘helper block’ within the current template.

Graham

]]>