Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DnnPackager build targets disabled by default for additional build configurations #49

Closed
dazinator opened this issue Feb 16, 2016 · 1 comment

Comments

@dazinator
Copy link
Owner

DnnPackager msbuild targets (the msbuild logic that handles producing install zip when you build) are only enabled by default for Debug and Release builds, if you create a new msbuild configuration then DnnPackager build targets do not run automatically. To make DnnPackager run you currently have to set the msbuild propery:

RunDnnPackager

  <PropertyGroup Condition=" '$(Configuration)|$(Platform)' == 'Client|AnyCPU' ">
    <DebugType>pdbonly</DebugType>
    /// shortened for brevity
    <RunDnnPackager>True</RunDnnPackager>
  </PropertyGroup>

This will catch people out. Change it so that DnnPackager always runs by default, but people can instead disable it if they want to.

@dazinator
Copy link
Owner Author

To stop DnnPackager running for a particular build, set the msbuild property:

<RunDnnPackager>False</RunDnnPackager>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant