Even if the module is a seperate SLN?
Yes it already referenced through source code by the abp studio import module, but if i dont build the module I will have in my main application reference issues. So as part of docker deployment strategy do you advice to build the module and copy it? Since for my application it does not belong to it directly, it depends on it
It is already referenced by the import from abp studio, but there is no way to avoid the clean and build for the seperated module that case.
I created a new module for my tiered application via abp studio, and was able to manage dependency after building the solution of the module. The thing is whenever i change anything in the module i need to dotnet clean and rebuild in order to take effect which is normal. But when I want deploy what is abp's approach for the modules. Should I pack it and put it on Nuget? if so, it is not feasible from our side to have a private nuget. what is abp's approach for such issue?
