Repository navigation
VersionConverter

This package modifies the DevExpress references in all Xpand.XAF.* assemblies to match the target project DevExpress version.
3 years ago I develop a my cool 5 xaf modules about X domain. I used the Xpand.VersionConverter nuget package, I compiled them and publish on Nuget.
3 years passed and I want to use them in a new project. I just need to install the nuget packages and they will work even if DevExpress assemblies names change every year (Major builds). This is the result of Xpand.VersionConverter that patches the version on each build. The support cost for my XAF modules closes to zero.
The alternative is to have a full Continuous Integration pipeline and support it (VERY COSTLY), a version strategy bound to DevExpress versioning just for being able to republish the packages.
You might say that do not even know whats a CI (Continuous Integration) or perhaps I do not use a CI, but think again, storing the project, taking backups, git repository, open visual studio, Ctrl+F5 is actually a CI.
-
Xpand.VersionConverterbefore the consumer project is build will change the version of all assemblies in the host package to match the DevExpress version of the consumer project. - If the package fails to detect the DevExpress version used from the consumer project due for e.g to indirect references you can help it with the DevExpressVersion msbuild property.
- The patching requires locking so the the patched packages are flagged to avoid locks in subsequent builds. To remove the flags you can use the Remove-VersionConverterFlags cmdlet.
- To troubleshoot you can enable verbose logging you can set the Environmental VersionConverterVerbose to 1 and an extensions.log will be created in the package directory.
- Xpand.Versionconverter is already a dependency to packages that use DevExpress assemblies in this repository.
Install-Package Xpand.VersionConverterUse main project issues