DnnPackager
DnnPackager copied to clipboard
Automate the packaging logic for your DotNetNuke projects, deploy to your IIS from within Visual Studio.
Here's the **Weekly Digest** for [*dazinator/DnnPackager*](https://github.com/dazinator/DnnPackager): - - - # ISSUES Last week, no issues were created. - - - # PULL REQUESTS Last week, no pull requests were created,...
Here's the **Weekly Digest** for [*dazinator/DnnPackager*](https://github.com/dazinator/DnnPackager): - - - # ISSUES Last week, no issues were created. - - - # PULL REQUESTS Last week, no pull requests were created,...
https://github.com/cantarus/PolyDeploy DnnPackager v3 will support deployment via: 1. Traditional URL mechanism (i.e < dnn 8) 2. Newer Mechanism that works with locally hosted (IIS) websites only But for v3.1 should...
For the v3.0 release I am going to make the following changes: 1. Installing the DnnPackager nuget package into a project will no longer give you any deployment or debugging...
At the moment, DnnPackager will include your target assembly, but for example if you need to include additional assemblies, then you need to modify some msbuild properties to tell DnnPackager...
@nvisionative - do you know if Dnn9 still honours having multiple manifest files in an install package, like this: manifest.dnn manifest.dnn5 And it will pick the correct one at install...
90% of my in development updates are Javascript and CSS changes. After each change I execute "Install-Module websitename" and then refresh the browser to see and test the change. The...
I would like to call install-module outside of Visual Studio / Package Manager Console. Use cases: - Use it within VS Code - Batch Builds/ installs in other build environments,...
Are IIS Applications supported? And what would be the WebSiteName in that case? Example: 