Back in October/November 2010 I started to look at the conversion from C# to VB.Net and had some discussions with tiago.
Unfortunately due to family commitments and illnesses within the family I was unable to to really get started.
If you look back to the discussions in Oct/Nov 2010 you will see that the decision was made to start from scratch with the latest templates rather than try and update the original VB .Net templates as too much had changed.
I was also thought to be a good idea to only translate the output and to leave the codesmith code in C#.
I still think that is the best way to go as it will be easier going forward to identify further changes to the codesmith code.
Also as neither I nor tiago had a full version of codesmith (tiago said he used notepad++ for editing), to enable easier editing the codesmith templates where renamed to *.asp so that they could be edited in VS which would think they were asp code and give
There is still a lot of hand coding to do to get CSLAGEnFork to output for VB.Net but I do think it is a very good idea.
I am wiling to help and again have more time to devote to the task.
If there were 2 or 3 people willing to help then we could share out the codesmith code and get started.
My preference would still be to leave the codesmith code as C# and convert the output code to VB.Net to make further updating easier.
We will need help from tiago to identify the code with CSLAGenFork that outputs C# code rather than the C# code being output from the templates.
e.g. tiago told me there is CslaTemplateHelperAdded.cs and so there would need to be VBCslaTemplateHelperAdded.cs that outputted the VB.Net equivalent.
I would think there are other routines that would need VB equivalents and tiago would be the best person to identify them.