Closed MarcelBPM closed 7 years ago
@andydandy74 what do you propose here - that we improve the documentation for developers on deploying their packages?
Not my issue. Not proposing anything. Just added the link to the discussion the OP was referring to.
Improved documentation would be great @mjkkirschner !
At this point, we're not sure what's causing this and people's IT & network setups vary wildly, so would be good to at least understand why/what changed.
Another user on the forum posted this:
https://forum.dynamobim.com/t/packages-on-local-network/15888
Which might be of help
Marcel
We have the same issue. Re-pathing to anywhere on the local drive works fine. As soon as it moves to a network drive the packages disappear from the library. They still show in "manage packages" but no content. Have tried with 1.2.1, 1.3.0 and 1.3.2. Have tried unblocking all the files in the bin folders.
can you try having IT add your network drives as trusted sites: https://technet.microsoft.com/en-us/library/bb496428.aspx
The note on that article seems to imply that something has changed between .net runtime 3 and 4 with regard to CAS - perhaps we built 1.0 against 3.x or users have now installed newer .net runtimes - which might cause a change in behavior.
more info, this seems to shed some more light: https://docs.microsoft.com/en-us/dotnet/framework/app-domains/running-intranet-applications-in-full-trust
last one: https://superuser.com/questions/44503/how-do-i-tell-windows-7-to-trust-a-particular-network-location
not sure if this applies anymore with windows 10 but I would give it a shot.
personally, I develop while storing some dlls in network drives and had to add that drive as a trusted site using IE....
Once IT added the server location to trusted sites all the packages showed up again. Thanks for the tip @mjkkirschner
This worked for me too.
please reopen if using trusted sites has not resolved the issue.
Hello all, I have completed the steps listed in @mjkkirschner "last one" link. I have done this to my computer only and the Packages with .dll files still are not there. Does this need to be done to the network server itself?
I am the one who started the post @MarcelBPM linked above. My packages were working for about 2 weeks but as of today they no longer show up. Dynamo and Revit have not changed.
You must add the network share location to your trusted sites. You must also unblock the dlls.
I have added the network share location to my computers trusted sites. I just copied the file path into "Add this website to the zone:" filed and clicked Add. Is this not the correct way (It did change the file path when added)?
.dll files are not blocked on our network.
I restarted my computer over the night ans it all seams to be working again. I had closed and reopened revit several times yesterday and that did not help. Restarts do some strange things.
All is working now :/?
I'm having this problem and haven't found any solutions yet.
We've tried adding the network drives as trusted sites and that hasn't solved it.
The other weird thing is that the .dll packages show up in Revit 2018 for me (and only me, as I have elevated privileges - they don't show up for our "normal" user), but not in Revit 2017. I even tried putting the packages in my appdata folder and that didn't work either in Revit 2017.
Any thoughts?
Dynamo version 1.3.1
Windows 10
What did you do?
Installed Dynamo 1.3.1
What did you expect to see?
All packages from the network folder loaded
What did you see instead?
A few Packages loaded, but not all. Asked the Dynamo Forum. They suggested that it had to do with .dll blocking, but it worked perfectly normal in 1.3.0, (nothing changed on the network side), so this cannot be the issue.