Sounds like your brief stop in AUS was not without a bit of excitement... Got relatives in Adelaide and they too are 'feeling the heat'. At one time, considered taking the family out there too - guess events like this truly coin the 'grass is always greener' phrase with a sliver of irony.
Anyway, re the <%%> sections. These are standard template placeholders and conatain boiler code that is a mixture of variables (the bits in the <%%> delimeters) and hardcoded program code. Typical examples would be something along the lines of:
public partial class <%= table.TableRowNameNoPrefix %>
The generated code would come out as a literal of:
public partial class Article
So, it's safe(ish) to say that you could change all the bits that weren't inside the <%%> sections to VB
code and those variable sections would be plugged into the program code without worry.
The only caveat here is that some of the <%%> code actually calls methods in the 'Custom Code' window, which in the current templates may well return a string of c# code. So, you'd also need to look at those methods in the 'Custom Code' window and translate where neccesary. An example in the \Table\bll_class.cs.tpl would be this bit:
<%= GetPropertyValue(table.Columns[i]) %>
as this method would return property getters in c#. You'd change the code in the Custom Code (GetPropertyValue) to return a VB
representation of the getter. Likewise with the section below that (<%= SetPropertyValue(table.Columns[i]) %> ). And so on, working out what return values in the Custom Code had to be made into VB
syntax. The actual code in the methods in the custom code section would remain untouched, only the value being returned would have to be changed.
Hope i'm making sense here as i seem to be more jetlagged than you are by the sounds of it!!
Email me directly if you have any issues. It would certainly be greatto have a VB
version of these templates 'out there' and I'm willing to work thro this with you in order to deliver a nice flexible solution that fits both camps.