during the installation of this package the following code is triggered:
# Modify initialization module namespace
$infrastructureSourcePath = Join-Path $toolsPath ".\Infrastructure"
$infrastructurePath = Join-Path $sitePath "\Infrastructure"
if (-Not (Test-Path $infrastructurePath))
Copy-Item $infrastructureSourcePath $infrastructurePath -Recurse
Add-ProjectItems $project $infrastructurePath
$initializationModulePath = Join-Path $sitePath "\Infrastructure\InitializationModule.cs"
Set-NameSpace $initializationModulePath $project.Properties.Item("DefaultNamespace").Value.ToString();
When there is already an Infrastructure folder is created, the installation fails, and potentially the user can be quite busy finding the reason why the project fails.
We will look into this. Thank you for bringing this into our attention.
The bug was fixed and will be released in upcoming release (probably Commerce 10.6.0)
A bit late, but thanks! :)
Makes my updates a lot quicker. Reverting my configsource approach before a I start with updates is time consuming.
Can you also take look ath this one? http://world.episerver.com/forum/developer-forum/Problems-and-bugs/Thread-Container/2017/6/installation-nuget-package-episerver.commerce.core/?pageIndex=1#reply