Closed MagneGanz closed 9 months ago
I will test it asap... I have to admit I made a larger refactoring and released 6116... which failed in a large number since a made a really bad error... so I worked hard to fix all that crap in 6119... however, I could not test it all, but had to release at least those errors I found. I will return to you as soon as I can, and sorry for the inconvenience.
I have now tested the node in a completely clean rvt file, and I can't reproduce your error
By the way, since you are using Dalux, I presume you are a Dane like me... or at least from Scandinavia :-)
Hi. We use dRofus that is a Norwegian software solution for Asset database. The problem however, is that dRofus tend to create Shared Parameters, when it should not, thus giving us duplicates. The Orchid Package help us to clean that up. A collegue of mine got the error first, because he used the latest version. I upgraded and got the same error message. It's a bit odd that you are not able to reproduce it. We'll just have to wait and see if more users have the same experience as us.. Thanks for the support.
It could be a conflict with a specific add-in maybe?
ahhh... sorry yes, dRofus, which I also have been using on some projects :-)
Could you send me the graph, so I could test it? one error I could think about is if another package should include assembly files, but why then does the build 6080 work beats me. So just for the record could you also include your list of other packages?
When I compile my package, I am using the latest versions of dynamo at any time, by looking up Nuget and downloading the latest Dynamo build available automatically.
did you find a solution?
IT could be an issue that another package does include the assembly files from Dynamo, however, this is only a problem if it is newbies that code a package. It is very well-known among the good codes not to include any dynamo assembly files. I am not aware if any other loaded plugins could cause any problems!?
…and just for the record, I presume that this could be a larger problem when we get Revit 2025 since this version will mark a large change, namely that we will move from .net4.8 (Framework) to .net8.0 (Core) … a really huge step.
I will close this issue, due to no response
Revit 2023. Build 6119 Tried: Document.SharedParameters - did not woks, says "contact Author".
Downgraded to Build 2.16.4.6080 and it works fine.