We strive to ensure that the CSLA templates are backwards compatible with previous versions. However, in some circumstances we break backwards compatibility to progress the platform. When we do break backwards compatibility, we ensure that the benefits of breaking compatibility greatly outway the benefits of not breaking compatibility. Please refer to this document when upgrading the CSLA Templates to ensure that you have the smoothest experience possible.
...
| Warning |
|---|
| It is strongly recommended to check in your solution and/or templates into Source Control or making make a backup before continuing. |
...
| Info |
|---|
| Please follow the guides for downloading and installing the CSLA Templates before continuing. |
...
| Info |
|---|
| If you are Installing a new version of Visual Studio, you must rerun the CodeSmith Generator installer to ensure Visual Studio Integration is installed. |
After you have verified that your projects are targeting the correct version of the .NET Framework, the next step is to update your assembly dependencies. You can do this by right clicking the CSLA assembly references in Solution Explorer and selecting remove. You must do this for all of your projects. This is required , because CodeSmith Generator will not update existing assembly references, it will only add them if they do not exist.
...
The next step is to update all existing Generator Project files. The Generator Project files will continue to point to the previous version of the templates if you don't update each template outputs output's paths. The fastest way to update a Generator Project file is to open it with notepad. Once you have opened the Generator Project file, you will want to update each propertySet's template node path to point to the current location as shown below.
...
| Info |
|---|
| If you have Visual Studio open and had previously opened Manage Outputs in Visual Studio. Then , then you will need to restart Visual Studio before the next step. You need to do this, because the previous template assemblies will be loaded into the AppDomain. |
...
The next step is to regenerate by building the solution or right clicking the Generator Project and selecting build and check for template compile and generation errors in the output window.
- If you see any errors about template file not found, then you will need to go to the previous step and ensure that the template output mentioned has the correct propertySet template node path.
- If you are seeing an error that deals with a template property not being able to be set. Please check the release notes, to see if a property has been removed. If it has, or you are getting an error you can follow the previous step, but remove the property XML node in question and repopulate it via Manage Outputs. This is very rare if you do encounter this issue.
- Unable to compile or generate template. Please contact support with the full stack trace / output window and we will take a look into the issue.
...