Closed apobekiaris closed 9 months ago
The pre-release 4.221.3.0 in the Reactive.XAF lab
branch includes commits that relate to this task:
To minimize version conflicts we recommend that you use the Xpand.XAF.Core.All, Xpand.XAF.Win.All, Xpand.XAF.Web.All packages. Doing so, all packages will be at your disposal and .NET will add a dependecy only to those packages that you actually use and not to all (see the Modules installation-registrations youtube video).
Please update the related Nuget packages and test if issues is addressed. These are nightly nuget packages available only from our NugetServer.
If you do not use these packages directly but through a module of the main eXpandFramework project, please wait for the bot to notify you again when integration is finished or update the related packages manually.
Thanks a lot for your contribution.
In the screencast:
Account
that derives from BaseObject
and already has a Guid Oid key
. Additionaly we add a Name
and a Secret
property.StoreToDiskAttirbute
to serialize the Secretnew Account
and set only its Name
.Closing issue for age. Feel free to reopen it at any time.
.Thank you for your contribution.
A working implementation existis in Reactive module, create a standalone package from it.
it is common practice when developing with Xaf to drop the database on each major change and let Xaf recreate from scratch. What if you want to add initial secured data?
You could use the updater and somehome code it there e.g. Azure Vaults or Enviromental Variables that point to a file exist only locally etc. But there are many problems with this approach. Think for example that your objects maybe created later and not in the Updater by parsing the results of a web service.
To save your self from such headaches and have your objects initialized correctly you can use the
StoreToDisk
package.