Page Comparison

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.

...

...

...

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.

...

...

The next step is to regenerate by building the solution or . You can do this by right clicking the Generator Project and selecting build and check . Next, 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 If you are unable to compile or generate template. Please the template, please contact support with the full stack trace / output window and we will take a look into the issue.

...

• upgrading from a minor version of CSLA (EG., 4.1 to 4.2), then chances are you are running into a bug with the templates. Please contact support and we will get this taken care of.
• upgrading to a major versions of CSLA (EG., 3.x to 4.x), then please check the release notes or upgrade documentation below.

...

It is highly recommended that you read over the official CSLA Documentation when upgrading between versions of CSLA. This ensures that you are aware of all of the changes that will occur in your application.

...

Before you continue this step, please ensure that you have followed the previous upgrade guide and have regeneratedhave regenerated. You will notice that there are some build errors.  This is due to the entity partial classes are not regenerated classes not being regenerated and there are some required changes for Rules or for Silverlight when migrating to CSLA 4.x.

...

There were major changes to Rules in CSLA 4.0. You will need to update every business objects object's non generated partial class (E.G., Account.cs or Account.vb).

...

protected override void AddAuthorizationRules()

Protected Overrides Sub AddAuthorizationRules()

public static void AddObjectAuthorizationRules()

Protected Shared Sub AddObjectAuthorizationRules()

...