C#Builder 1.0
ECO Update for Architect Edition
Release Notes
=======================================================
This file contains important supplementary and late-breaking
information that may not appear in the main product
documentation, and supersedes information contained in other
documents, including previously installed release notes.
Borland recommends that you read this file in its entirety.
Important: C#Builder must be closed before installing this
Update
Pack.
=======================================================
CONTENTS
* ISSUES ADDRESSED BY THIS UPDATE PACK
* NEW INTERFACES
* KNOWN ISSUE
* FILES INSTALLED BY THIS UPDATE PACK
* INSTALLING THIS UPDATE PACK
* VERIFYING THAT THE UPDATE WAS SUCCESSFUL
=======================================================
ISSUES ADDRESSED BY THIS UPDATE PACK
This Update Pack provides the following ECO improvements:
* Strengthened OCL support by:
- fixing derived relations
- improving support to write and use constraints
- making the list of dirty objects evaluatable
- ensuring string representation of attributes to be properly
re-evaluated on underlying changes
- fixing truncation of long OCL strings when reading them
back from the source
* Coding is simplified by:
- fixing a problem with clearing single links by assigning nil
- exposing more feature-rich services (invalidation and
transactions)
- fixing a problem with deleting the last element in a list
showing in the GUI
* Rapid prototyping is enhanced by:
- templates now include support for Autocontainers
- Autocontainers now correctly show inherited attributes
* Modeling power has increased by:
- fixing support for cross-package associations
- exposing the setting of association-end composition
IMPORTANT NOTE: Code generation for association-ends has been
amended to fully support cross package linking. While this is
done automatically for new code, old code must be manually
updated to include the fully qualified name of the
association. The format of the old code is:
[UmlMetaAttribute("association",
typeof(<<package>>.<<association>>),
Index=<<index>>)]
The format of the new code is:
[UmlMetaAttribute("association",
typeof(<<namespace>>.<<package>>.<<association>>),
Index=<<index>>)]
The old format associations will not appear in the diagram
until the code is manually updated. Use the following
procedure to update those associations. The procedure assumes
a package named CoreClassesPackage, a project named EcoApp,
and a namespace named EcoApp (the namespace name, by default,
is the same as the project name).
1) Make a back-up of CoreClasses.cs.
2) Open the EcoApp project in the IDE.
3) Ensure that all diagram views are closed.
4) Choose "Search | Find in Files" and find the following text:
UMLMetaAttribute("association"
This will show how many changes are required
and the line
number of each. There are two UML custom
attributes for each
association in the model.
5) Open CoreClasses.cs in the Code Editor.
6) Choose "Search | Replace" and provide the following:
Text to find: CoreClassesPackage.
Replace with: EcoApp.CoreClassesPackage.
Prompt on replace: ON
Scope: Global
Origin: Entire scope
7) Click the Replace All button. Click Yes to each change.
8) Save and close the project.
9) Reopen the project. The associations should now be visible in
the diagram.
* The following entries from Quality Central have been addressed:
6051 - No composition/aggregation is exposed in the tagged values
6040 - Object constraints are always null
6039 - TaggedValues.Count is always 0
=======================================================
NEW INTERFACES
This Update Pack provides the following new interfaces:
IPersistenceService.Unload(IObjectList objects)
The specified objects are unloaded from memory. This recycles
memory, and allows the objects to be reread to reflect any
changes made in the database.
IPersistenceService.Unload(IObject obj)
The specified object is unloaded from memory.
IUndoService.StartTransaction()
Starts an in-memory transaction.
IUndoService.CommitTransaction()
Commits an in-memory transaction. Must match a corresponding
call to StartTransaction().
IUndoService.RollbackTransaction()
Rolls back an in-memory transaction. Must match a corresponding
call to StartTransaction(). All changes made inside the
transaction are lost.
=======================================================
KNOWN ISSUE
Due to the interaction between the modeling tool and the Code
Editor, caution is required when editing methods marked as
[EcoAutomaintained]. When manually editing code in a method
marked as [EcoAutomaintained], your code may be automatically
removed or modified without notification. This may result
in model information being irrecoverably corrupted. To avoid
this behavior, always remove the [EcoAutomaintained] attribute
before editing any method bodies.
=======================================================
FILES INSTALLED BY THIS UPDATE PACK
This Update Pack updates or adds the following files:
<Common Files>Borland SharedBDSShared
Assemblies1.0Borland.Eco.Core.dll
<Common Files>Borland SharedBDSShared
Assemblies1.0Borland.Eco.Handles.dll
<Common Files>Borland SharedBDSShared
Assemblies1.0Borland.Eco.Interfaces.dll
<Common Files>Borland SharedBDSShared
Assemblies1.0Borland.Eco.Ocl.ParserCore.dll
<Common Files>Borland SharedBDSShared
Assemblies1.0Borland.Eco.Persistence.dll
<GAC>Borland.Eco.Core.dll
<GAC>Borland.Eco.Handles.dll
<GAC>Borland.Eco.Interfaces.dll
<GAC>Borland.Eco.Ocl.ParserCore.dll
<GAC>Borland.Eco.Persistence.dll
<GAC>policy.7.1.Borland.Eco.Core.dll
<GAC>policy.7.1.Borland.Eco.Handles.dll
<GAC>policy.7.1.Borland.Eco.Interfaces.dll
<GAC>policy.7.1.Borland.Eco.Ocl.ParserCore.dll
<GAC>policy.7.1.Borland.Eco.Persistence.dll
<InstallDir>BinBorland.Eco.Handles.Design.dll
<InstallDir>BinBorland.Studio.Together.dll
<InstallDir>BinBorland.Together.EcoDiagram.dll
<InstallDir>BinBorland.Together.EcoPerformers.dll
<InstallDir>BinBorland.Together.EcoSourceModel.dll
<InstallDir>ObjreposECOEcoSpaceTemplate.cs
<InstallDir>ObjreposECOEcoWinFormTemplate.cs
<InstallDir>ObjreposECOWinFormTemplate.cs
<InstallDir>readme_upd1.rtf
<InstallDir>readme_upd1.txt
=======================================================
INSTALLING THIS UPDATE PACK
This is a self-executing Update Pack. Double-click on the file
to begin the installation and follow the prompts.
Note: The Update Pack can not be removed after it is installed.
=======================================================
VERIFYING THAT THE UPDATE WAS SUCCESSFUL
The final page of the Update Pack installation wizard indicates
whether the update was successful. Additionally, after you have
installed the Update Pack, you can verify the version
information for the following files:
Server Response from: BDN9A
