-
Notifications
You must be signed in to change notification settings - Fork 6
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
Adding GetEvents component #274
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, the component is exposed correctly
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/azp run Dynamo_Toolkit.CheckInstaller |
Azure Pipelines successfully started running 1 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pawelbaran , this didn't crash for me. Did you follow the procedure in the That being said, when testing for the crash, I noticed I couldn't create the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems to be working fine on both 2018 + 2.0 as well as 2020 + 2.3 now 👍 LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm still happy
/azp run Dynamo_Toolkit.CheckInstaller |
Azure Pipelines successfully started running 1 pipeline(s). |
NOTE: Depends on
BHoM/BHoM_UI#331
Issues addressed by this PR
See BHoM/BHoM_UI#331
Additional comments
If you found yourself in the situation where the component fails (silently) to create itself, make sure to manually clean the BHoM folders in
AppData\Roaming\Dynamo
for 2.3 (core and Revit). It seems that the installer is still copying the dlls there therefore creating a conflict with the dll inProgramData/BHoM
.