Conversation
| <PlatformTarget >x64</PlatformTarget> | ||
| <Prefer32Bit>false</Prefer32Bit> | ||
| <Platforms>NET100</Platforms> | ||
| <Platforms>NET100;NET80_DA</Platforms> |
There was a problem hiding this comment.
I'm so confused, I thought for 2026 we would not be supporting net 10? Is this because of net10 back port?
There was a problem hiding this comment.
YEs, I know
ANd yes, because of backport
| <DCoreLibSubFolder>net10.0</DCoreLibSubFolder> | ||
| <TargetFramework Condition="'$(Platform)' == 'NET80_DA'">net8.0-windows</TargetFramework> | ||
| <DCoreLibSubFolder Condition="'$(Platform)' == 'NET80_DA'">net8.0</DCoreLibSubFolder> | ||
| <DCoreLibSubFolder Condition="'$(Platform)' == 'NET100'">net8.0</DCoreLibSubFolder> |
There was a problem hiding this comment.
that is supposed to be net10. Will fix
| </Reference> | ||
| </ItemGroup> | ||
| <Target Name="Copy dll" AfterTargets="Build"> | ||
| <Copy SourceFiles="$(PkgGregRevitAuth)\lib\$(DotnetVerSubFolder)\GregRevitAuth.dll" DestinationFolder="$(OutputPath)" /> |
There was a problem hiding this comment.
we copy this because DA does not provide it?
|
@pinzart90 did you verify that Revit.All builds? |
| @@ -0,0 +1,106 @@ | |||
| # Build System Cleanup — Open Questions & TODOs | |||
|
|
|||
| These are known issues and open design questions in the build system that need | |||
There was a problem hiding this comment.
can you have go through this and note what is now done after this PR? Have an agent do this?
|
| if (!d.IsLinked) | ||
| { | ||
| CurrentDBDocument = d; | ||
| break; |
There was a problem hiding this comment.
I don't remember seeing this code before - so it just picks the first doc, how could more than 1 doc be loaded?
|
I don't think we'll merge this PR into 2026. This is going to live as a branch I imagine. |
| { | ||
| // | ||
| // Summary: | ||
| // Save the revit document to the default result.rvt file. |
|
|
||
| RevitServices.Transactions.TransactionManager.SetupManager(new RevitServices.Transactions.AutomaticTransactionStrategy()); | ||
| // TODO: do we need element binding in Design Automations? | ||
| ElementBinder.IsEnabled = true; |
There was a problem hiding this comment.
good question... If the rvt has elements that would be rebound then it could be good - but I feel like we should default to off... element binding mostly make sense when you have the same call sites executing repeatedly like when interacting with a graph - we can't have that here.
|
@pinzart90 - at some point it would be good to take this branch / set of commits / this PR and try to generate/propose a real plan for getting this merged with D4R - long term do you think the solution is splitting of the addin into 2 addins or sticking with the defines? |
Please Note: 1. Before submitting the PR, please review [How to Contribute to Dynamo](https://github.com/DynamoDS/Dynamo/blob/master/CONTRIBUTING.md) 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](https://github.com/DynamoDS/Dynamo/wiki/Choosing-a-Pull-Request-Template) 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 (FILL ME IN) This section describes why this PR is here. Usually it would include a reference to the tracking task that it is part or all of the solution for. ### 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](https://github.com/DynamoDS/Dynamo/wiki/Coding-Standards) - [ ] The level of testing this PR includes is appropriate - [ ] User facing strings, if any, are extracted into `*.resx` files - [ ] Snapshot of UI changes, if any. ### Reviewers (FILL ME IN) Reviewer 1 (If possible, assign the Reviewer for the PR) (FILL ME IN, optional) Any additional notes to reviewers or testers. ### FYIs (FILL ME IN, Optional) Names of anyone else you wish to be notified of
### Purpose Add default output folder ### 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](https://github.com/DynamoDS/Dynamo/wiki/Coding-Standards) - [ ] The level of testing this PR includes is appropriate - [ ] User facing strings, if any, are extracted into `*.resx` files - [ ] Snapshot of UI changes, if any. ### Reviewers (FILL ME IN) Reviewer 1 (If possible, assign the Reviewer for the PR) (FILL ME IN, optional) Any additional notes to reviewers or testers. ### FYIs (FILL ME IN, Optional) Names of anyone else you wish to be notified of
Please Note:
DynamoRevitrepo 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 aLGTMlabel is added to the PR.Purpose
(FILL ME IN) This section describes why this PR is here. Usually it would include a reference
to the tracking task that it is part or all of the solution for.
Declarations
Check these if you believe they are true
*.resxfilesReviewers
(FILL ME IN) Reviewer 1 (If possible, assign the Reviewer for the PR)
(FILL ME IN, optional) Any additional notes to reviewers or testers.
FYIs
(FILL ME IN, Optional) Names of anyone else you wish to be notified of