As shown in the picture whebn I try to replace the dependency, it keeps looking for something else and indeed cannot find it!
Same happens if I remove the dependency and add a new one. It still keep looking for the wrong one.
Am I missing something?
hm… so how can we reproduce this?
also are you experiencing different behavior when you try to do the same in latest stable 6.7 and latest 7.0 previews?
Yes, I’ve tested this with 6.7 as well, but I can’t think of a clear reproduction process.
Here’s the situation:
I have a foo.dll that references some standard .NET assemblies such as gRPC and Protobuf. Normally, you wouldn’t need to include those in the lib folder, you’d just have foo.dll and reference the gRPC assemblies directly in vvvv. However, in this particular case, foo.dll requires gRPC.Core. Meeh!
I referenced foo.dll in vl.bunraku and everything worked fine until I accidentally removed gRPC.Core, which foo.dll needs. That was entirely my mistake.
Now, when I try to remove or replace foo.dll, I get the error:
“File doesn’t exist”
The only workaround I’ve found is to create a new .vl file, add the DLLs again, copy over the definitions, and rename it.
So perhaps the real question is: why can’t I properly remove dependencies? The UI makes it look like they’re gone, but it seems they’re still hanging around.
Sorry this isn’t a fully reproducible bug report, but I’d appreciate any hints or pointers.
Merci
ok, i’m not sure i can follow entirely but in general: any .dll loaded by vvvv cannot be unloaded at runtime. even when you remove a reference, the .dll itself is still loaded. does this info help: Referencing Libraries | vvvv gamma documentation
Thank you @joreg
Yes, excatly! And as adviced on the graybook i started a forum thread :)
Just a note that I don’t get the “Attention: You have referenced the following assembly…” pop up; rather i see only the red highlight in the dependecy menu. When I hover on it, its reads: “File does not exists”
