How do I start using CslaGenFork?
- Download the latest version of CslaGenFork from this project Downloads section (MSI installer).
- Download the latest version of the templates from this project Downloads section (ZIP file). UNZIP the templates file somewhere handy (in case you want to edit them)
- Download the free CodeSmith version from
this CodeSmith link. This is version 2.6, an old free version. Just leave it there, no need to unzip as CslaGenFork will do it for you.
- Run the CslaGenFork MSI installer.
- Open CslaGenFork
- Go to Tools -> CodeSmith Extension...
- On the CodeSmith Extension Handler popup click Install, choose the CodeSmith ZIP file and click
Open. Now click Exit to go back to CslaGenFork.
- Go to Tools -> Locate Template Directory, choose the templates folder you chose in step 2. and click
Now you are ready to start using CslaGenFork. In no time you will be generating your first project.
NOTE - CslaGenFork expects you to use a user account with administrative privileges in order to change the template location folder and default project settings.
VERY IMPORTANT NOTE - As stated elsewhere, most advanced features of CslaGenFork will only work if you are using C# code generation and target CSLA40 or CSLA45 or the DAL targets.
What is the suggested way of using CslaGenFork?
You should use a source control system but you don't have to pay for it. Subversion/SVN is now a usable and very good choice, not to mention you can have a full system for free:
- create a database with proper Primary Keys and Foreign Keys
- create a project with CslaGenFork
- generate the source code
- commit the XML project file and the source code files to the repository
- edit the sources changing whatever you like and commit again - it's better to left the .Designer files alone and edit only the extended (non .Designer) files
- change the CslaGenFork project
- regenerate - only the .Designer files will be regenerated; in order to get freshly regenerated extended (non .Designer) files you must delete the old ones)
- commit the project file again
- use AnkhSVN "Show Changes" to help you keep the changes made previously that you want to keep
- commit the source files again
NB - The term "commit" is a SVN term for what SourceSafe, TFS, etc call "Check In".