Getting started with codesmith3.1-solved Oracle connection and Chinese Character Problems

Because I still use vs2003, only version 3.1 is available. In the past, versions 2.6 were used. All attacks are detected.ProgramIt's much more convenient.

I wrote "set codesmith to connect to the Oracle Database", which is about Oracle provider in codesmith2.6.Article.
Now 3.1 is used, and of course the same problem is encountered.

Solution: Go to codesmith's community, http: // community.codesmithtools.com/files/9/schemaproviders/default.aspx, and have an oracle schema provider in the folder. Download it and compile it yourself.

If the downloaded file is used directly, the Oracle provider may not be found in codesmith studio.
The solution is to openSource code. The system may prompt that schemaexplorer. dll cannot be found. Because oraclenativeschemaprovider appears in schemaexplorer of codesmith. DLL exclusion, and set schemaexplorer in the codesmith3.x installation location (c: \ Program Files \ codesmith \ V3.0 \ addins. DLL introduction, re-compile and compile schemaexplorer. using lenativeschemaprovider. DLL and the original downloaded schemaexplorer. using lenativeschemaprovider. DLL. config
Put the file in c: \ Program Files \ codesmith \ V3.0 \ schemaproviders (or equivalent) folder:, and finally add oracleprovider to schemaexplorer of codesmith.
Note: This method should be able to adapt to most codesmith, that is, download the corresponding source file (the version is a little different, but if the entire interface changes, then look for the response version) and introduce schemaexplorer in the installation file. DLL, re-compile, if successful, you can get the corresponding version of schemaexplorer. using lenativeschemaprovider. DLL. Then you can put it in the corresponding folder.

I will provide the originalCodeYou can download it. I hope it will be convenient for you.
Oraclenativeschemaprovider.rar

Chinese Character unsupported solution:
enable codesmith studio to set codesmith tools-> Option-> enable Unicode support
and then in the template: add responseencoding = "UTF-8" as follows:
<% @ codetemplate Language = "C #" responseencoding = "UTF-8" %>