Each upgrade of almost DCG is more convenient to bring the end user, this time is no exception. So what is the innovation of this DCG? Let's take a look, the changes in DCG are as follows:
Added a change reservation function. The advantage of the code generator is that the time-saving power is saving, so we choose it, but the code generator is not shortcoming, its shortcomings are also big, that is, each output will change the change after the output. This makes us very hurt our customers, and it is this for this to make us not dare to use the code generator to generate second. In order to overcome the above reasons, the author upgraded the DCG again, expands its function, reserves the modification when it is generated again by the output file reserved information. Examples are as follows: <% @ template language = "vb"%> <% @ parameter name = "ns" datatype = "string"%> <% @ parameter name = "oldfilepath" DataType = "string"%>
<% Dcg.reservedspace.beginsymbol = "/ * * /"%> <% dcg.reservedspace.endsymbol = "/ * - * /"%> <% dcg.reservedspace.oldFilePath = OldFilePath%> <% dcg.reservedSpace .GeneratedEFault Value = (DCG.ReServedSpace.oldFilePath is nothing)%> namespace <% = ns%> {public <% - seray -%> class base {public void dosomething () {<% - // Todo <% "algo" %%> -%>}}} Sets the change retention function by dcg.reservedSpace, keeping the syntax in the template is <% - reserved space -%>, where reserved space is the default value, that is, when dcg.reservedspace .GeneratedeDefaultValue will output the default value when it is a false or last modification. %> Strings Output in the label. In the previous version, you want to output%> not an easy task in a label, because it represents an end of a label, but now by% in the label %> To the%> of the%> of the point can output%>. Also want to output <% instead of using <%% instead of the label.
All DCG version 1.4.1.1 changes are fully compatible.
