ModelMapper generation happens too often

apobekiaris commented 4 years ago

according to the wiki it happens when

If the assembly does not exist in path.
If the ModelMapper module ModuleVersionId changed.
If any of the mapped types assembly ModuleVersionId changed.
If Mapping customization changed. (Read more on How to customize a Map)

However it is possible to detect if a custom map is used and if not avoid generation checking again XAF or Xpand version of the existing assembly.

apobekiaris commented 4 years ago

additionally it should also be same trivial to generate two assemblies one for the predefined and one for the custom. The predefined mapping which is slow, will happen only once and only when u upgrade or not found in path

apobekiaris commented 4 years ago

this encasement will also improve the design time experience and probably hidden configuration problems like the one @dsikic has at #778

expand commented 4 years ago

We will try to answer all questions that do not require research within 24hr. To prioritize cases that require research we use the following labels in order. For all other issues the posting time is respected.

❇️ Exclusive-Services

This case is prioritized.

apobekiaris commented 3 years ago

Issue is deprioritized as no Assignee found and scheduled for auto-close if no activity in the next 60 days. Thanks a lot for your contribution.

apobekiaris commented 3 years ago

The pre-release 2.201.22.1 in the DevExpress.XAF lab branch includes commits that relate to this task:

ModelMapper: Separate Predefined assembly #785

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).

Released packages:

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.

expand commented 2 years ago

Closing issue for age. Feel free to reopen it at any time.

.Thank you for your contribution.

eXpandFramework / eXpand

ModelMapper generation happens too often #785