Skip to content

Conversation

@QilongTang
Copy link
Contributor

@QilongTang QilongTang commented Mar 28, 2019

Please Note:

  1. Before submitting the PR, please review How to Contribute to Dynamo
  2. Dynamo Team will meet 1x a month to review PRs found on Github (Issues will be handled separately)
  3. PRs will be reviewed from oldest to newest
  4. If a reviewed PR requires changes by the owner, the owner of the PR has 30 days to respond. If the PR has seen no activity by the next session, it will be either closed by the team or depending on its utility will be taken over by someone on the team
  5. PRs should use either Dynamo's default PR template or one of these other template options in order to be considered for review.
  6. PRs that do not have one of the Dynamo PR templates completely filled out with all declarations satisfied will not be reviewed by the Dynamo team.
  7. PRs made to the DynamoRevit repo will need to be cherry-picked into all the DynamoRevit Release branches that Dynamo supports. Contributors will be responsible for cherry-picking their reviewed commits to the other branches after a LGTM label is added to the PR.

Purpose

DYN-1739
As a Dynamo integrator, I would like to use Dynamo pdb files from release build for CER diagnosing.

This PR:

  1. Adds another nuspec file for a new nuget package @DynamoDS/dynamo Team will manage going forward internally to provide support for all Dynamo integrators
    image

  2. Improve console messaging by using @echo off when running this script so we do not log wrong information
    image

  3. Updates nupkg description for DynamoCoreRuntime

Declarations

Check these if you believe they are true

  • The code base is in a better state after this PR
  • Is documented according to the standards
  • The level of testing this PR includes is appropriate
  • User facing strings, if any, are extracted into *.resx files
  • All tests pass using the self-service CI.
  • Snapshot of UI changes, if any.
  • Changes to the API follow Semantic Versioning, and are documented in the API Changes document.

Reviewers

@scottmitchell @mjkkirschner

FYIs

@DynamoDS/dynamo

@mjkkirschner
Copy link
Member

LGTM

@mjkkirschner
Copy link
Member

hmm @QilongTang can we only provide our own .pdbs? I'm not sure we should distribute any pdbs but our own in this package. (ie remove cefsharp)

@QilongTang
Copy link
Contributor Author

@mjkkirschner I believe I have removed all the pdb files not owned by our team, please let me know if the final package sample looks OK for you guys.

</metadata>
<files>
<file src="*.pdb" target="lib\net47" />
<file src="*.pdb" target="lib\net47" exclude="CefSharp*.pdb;Helix*.pdb;MIConvexHull.NET Standard.pdb"/>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hmm, can we pull this out into a variable at the top of the file? we're going to forget to update this list.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we can do this because this is an XML with schema defined here: https://docs.microsoft.com/en-us/nuget/reference/nuspec#general-form-and-schema

@mjkkirschner
Copy link
Member

@QilongTang do we need to do anything else to get this uploaded automatically? If you are looking at this already - anyway to get the upload user into the new nuget dynamo org?

@mjkkirschner
Copy link
Member

@QilongTang yes, this should match however we distribute the source.

@QilongTang
Copy link
Contributor Author

QilongTang commented Mar 29, 2019

@mjkkirschner I don't think we need to do anything else rather than merging this. This will not go to public nuget so publisher will be our build machine on artifactory

@QilongTang
Copy link
Contributor Author

@mjkkirschner Updated to use all same licencing and year of copy right

@mjkkirschner
Copy link
Member

LGTM

@QilongTang QilongTang merged commit 7cbd0c7 into master Apr 1, 2019
@QilongTang QilongTang deleted the DynamoCoreSymbolsNuget branch April 1, 2019 04:56
@aparajit-pratap
Copy link
Contributor

@QilongTang do we really need to publish pdb's for test assemblies as well?

@QilongTang QilongTang mentioned this pull request Apr 1, 2019
7 tasks
@QilongTang
Copy link
Contributor Author

@aparajit-pratap @mjkkirschner For simplicity, let's skip all the test related pdb files see referenced PR

QilongTang added a commit that referenced this pull request Apr 2, 2019
* Alter build package batch file and create new nuspec

* Add comments and improve console messaging

* exclude pdb files not owned by Dynamo team

* Update all the licencing info
QilongTang added a commit that referenced this pull request Apr 2, 2019
* Kicking off DynamoCoreSymbols Nuget Package (#9608)

* Alter build package batch file and create new nuspec

* Add comments and improve console messaging

* exclude pdb files not owned by Dynamo team

* Update all the licencing info

* Exclude Dynamo Test PDB (#9615)

* Exclude Test PDB files

* Simplify the change

* nuget release
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.

4 participants