You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the client looks at the Current Directory, but it would be a nice feature to have, to be able to specify where the module zips are located on disk via cmd argument.
The text was updated successfully, but these errors were encountered:
Sounds like a good idea to me and if the DeployClient is proving useful to people off the shelf then the added flexibility will be appreciated I'm sure.
Introduced PackagesCrawler to encapsulate logic that will read all
installation packages full file paths. It enables the DeployClient to
read installation packages from a defined directory. It's no more
necessary to save installation packages beside the DeployClient.exe.
Encapsulated code in own method, that will write packages information to
console and cancels the execution if no packages were found in packages
directory, to get better readable code.
Added unit tests for new PackagesCrawler component.
Migrated Solution to Visual Studio 2019.
Updated DeployClient project to .Net Framework 4.8 to get it up to date.
Related issue: DNNCommunity#26
Currently the client looks at the Current Directory, but it would be a nice feature to have, to be able to specify where the module zips are located on disk via cmd argument.
The text was updated successfully, but these errors were encountered: