-
Notifications
You must be signed in to change notification settings - Fork 23
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
Release handling #73
Comments
As part of finalizing our release strategy for the new .NET Standard-based binary, we should change the name of the project (or at least the DLL that is produced) because right now it's |
Name change and .nupkg creation parts are in review. The part about releasing symbols and a debug release flow are not yet planned. |
Debugging symbols and Debug vs Release. We should make sure to push release version to NuGet and push release symbols to symbolsource.org. We should also use something else, like myget or VSTS to push debug versions for our own purposes or for select clients who need them for something...and also push debug symbols to symbolsource.org.
It's likely very little will change in the repo and is to just make sure we lock down this process and check all the boxes each time we push a release in the future. Mostly will just need to make sure to use the correct compiler flags and
nuget.exe
flags at release time.The text was updated successfully, but these errors were encountered: