Closed martinromby closed 7 years ago
@martinromby Can you check if the bin subfolder of the package contains a file called DynamoAutomation.dll ?
DynamoAutomation.dll is in the bin folder @andydandy74
In that case try unblocking the DLL. (You should find information on that on the forum...)
Hey, There are a couple of errors appearing in the install in both version 1.3.3 and 1.3.2. In 1.3.3 there are 2 missing nodes (yes I did unblock the dll). And in version 1.3.2 I can find the 2 missing nodes but another is now missing.
@martinromby Okay, I can reproduce this behaviour on my machine and unblocking the DLL in Dynamo 1.3.0 or 1.3.1 won't help (it does in 1.0.0 - but DA isn't compatible with that Dynamo version). I'll try to investigate this further this weekend.
Hey @andydandy74 just a follow-up on this. I managed to make it work but in a strange way.
What I did is: I forked DynamoAutomation opened it in Visual Studio via the GitHub extension, rebuilt it and replaced the files in the package. It still did not work.. but wait for it. Because of a different task I had to restart my computer and opened Revit 2016 and out of curiosity opened the Master Graph there and now I could see all the Nodes. Nothing was missing anymore. I then opened Dynamo Sandbox with Administrative rights and now it is working. This will change everything in regard to Revit workflow.
I now have another problem:
@martinromby @milotindragos - There is a new version of DA on the package manager. Please upgrade to that version and let me know if that fixes the problem of missing nodes.
@andydandy74 The 1.3.4 version seems to include the necessary nodes. Issue is solved.
Glad to hear it. Many thanks to @dimven for pointing me in the right direction.
@andydandy74 the new version works perfect. From the tests I did it has all the nodes and everything seams to work now. Thank you
Description
It seems that when setting up a new Dynamo installation with the latest version of DynamoAutomation package, some nodes are missing, i.e Process.ByPathAndArguments, Journal.PurgeModel, Journal.PurgeModels + more. These nodes seems to be used in the updated sample files, which properly means they still should be in the package. The nodes can be found in DynamoAutomation 1.3.2
DynamoAutomation 1.3.3
DynamoAutomation 1.3.2
Expected behaviour
I would expect that these nodes would be installed in the 1.3.3 installer.
My setup
Housekeeping
Please make sure these boxes are checked before submitting your issue: