Skip to content

Conversation

@Arvtesh
Copy link

@Arvtesh Arvtesh commented Feb 25, 2019

This should fix #84.

The build script is updated to create release assemblies as CI output. If I'm correct this should result in release assemblies pushed to NuGet package. Hopefully this will fix the issue linked above.

@jdnichollsc
Copy link
Contributor

Hi @RoryDungan, what do you think about this change? 👍

@RoryDungan
Copy link
Contributor

Yeah I think it looks good but I don't work at RSG any more. @kalvinpearce or @Borningstar can you merge?

@RoryDungan
Copy link
Contributor

Actually on second thought this might not be best. It won't actually fix #84 because Nuget packages never came from Travis, they're built manually.

Changing the Travis config won't necessarily affect that but we may want to keep using the debug version for running unit tests on Travis for better stack traces in the case a test fails. On the other hand maybe it's best to test the assembly that most closely resembles what should be on Nuget so maybe release is better. I don't think it makes a huge difference in this case.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

NuGet package contains non-optimized (Debug) assembly

3 participants