WEBfactory 2010

Symptom

A previously set property setting is not saved when reopening the project.

Cause

The control's serializer. The serialize and deserialize methods might not be correct.

Solution

Check the serialize and deserialize methods in the serializer.

Make sure that the property is not missing from the serializer and deserializer.

Example

(SymbolicText property as example)

The correct serializer code should look like:

properties.Add(new XElement("SymbolicText", node.SymbolicText))

The correct deserializer code should look like:

this.SetSafeValue(properties.Element("SymbolicText"), (string v) => node.SymbolicText= v);

Symptom

A previously set collection setting is not saved when reopening the project.

Cause

The control's serializer. The serialize and deserialize methods might not be correct.

Make sure that the property is not missing from the serializer and deserializer.

Solution

Check the serialize and deserialize methods in the serializer.

Example

(States collection as example)

The correct serializer code should look like:

#region Serialize       
        protected override IEnumerable<XElement> SerializeCollections(ICommonControlViewModel source)
        {
            var baseCollections = base.SerializeCollections(source);

            var sourceControl = source as WFExampleViewModel;

            var collections = new List<XElement>();
            collections.Add(this.GetSerializedStateConditions(sourceControl.States));            

            return baseCollections.Concat(collections);
        }        
#endregion

The correct deserializer code should look like:

#region Deserialize
        protected override void DeserializeCollections(XElement propertyCollectionsElement, ICommonControlViewModel 

target, Version version)
        {
            base.DeserializeCollections(propertyCollectionsElement, target, version);
            var node = target as WFExampleViewModel;

            this.DeserializeStateConditions(propertyCollectionsElement, node, node.States, version);
        }
#endregion

Symptom

The SmartEditor crashes when clicking a category in the Toolbox.

The SmartEditor crashes when dragging and dropping a control from the Toolbox to the Page.

Cause

The control's XAML is corrupted.

The assembly is not correctly specified in the SmartEditor mappings (WEBfactory 2010 \SmartEditor\Mappings), or the mapped assembly does not exist.

Solution

Check the bindings in the XAML:

Check the mapping of the control. Make sure that the assembly exists and is correctly mapped for SmartEditor.

Example

Text="{Binding Number}"

where Number is an int or is null, while it should be a non null string.

Symptom

The settings for a property are not applied when editing that property at design-time.

Cause

The control's XAML is corrupted or the ViewModel property is not notified.

Solution

Check the bindings in the XAML:

Make sure that the property setter calls RaisePropertyChanging and RaisePropertyChanged.

Example

(SymbolicText property as example)

A correct TwoWay binding should look like:

Color="{Binding Color, Mode=TwoWay}"

The property setter should look like:

set
 {
    if (symbolicText != value)
    {
        var changedEventArgs = new ValueChangedEventArgs<string>(symbolicText, value);
        RaisePropertyChanging(() => SymbolicText);

        symbolicText = value;
        SymbolicTextChanged.Raise(this, changedEventArgs);
        RaisePropertyChanged(() => SymbolicText);
    }
 }

Symptom

The settings for a property are not applied when editing that property at run-time.

Cause

AddXamlAttribute is misssing for that property.

Solution

Add AddXamlAttribute to the property.

Example

(SymbolicText property as example)

The code that is missing:

AddXamlAttribute("SymbolicText", SymbolicText);

Symptom

The settings for a collection are not applied when editing that collection at run-time.

Cause

AddXamlAttribute is misssing for that collection.

Solution

Add AddXamlAttribute to the collection.

Example 

(States collection as example)

The code that is missing:

AddXamlCollection(collectionXaml, "States", States);

Symptom

When running the project, the result in the web browser is a blank page.

For examples and other detailed information, please refer to the Creating Custom Controls for SmartEditor tutorial.

Case 1

Cause

Invalid Page.xaml (from projectName.Web/Build/Page.xaml):

Miss-typed code. The properties might have naming errors and invalid values.

Solution

Fix any miss-typed code. Check for naming errors and invalid values.

Case 2

Cause

Invalid Page.xaml (from projectName.Web/Build/Page.xaml):

A property is missing from the XAML because the AddXamlAttribute method is missing from the ViewModel.

Solution

Add AddXamlAttribute("PropertyName", PropertyName); to the ViewModel.

Case 3

Cause

Invalid Page.xaml (from projectName.Web/Build/Page.xaml):

Namespaces are missing from the XAML.

Solution

Check for missing namespaces and add them if needed.

Case 4

Cause

Assembly references are missing from the ViewModel

Solution

Add the assembly references to the ViewModel

Case 5

Cause

Namespaces are missing from the ViewModel.

Solution

Check for missing namespaces and add them if needed.