Closed TWith2Sugars closed 9 years ago
Have you tested this out by testing the full package and referencing out from a clean solution? I tried to get the type provider to play nicely with azure storage as a NuGet dependency but there were always problems around finding the dependency DLLs at compile time of client solutions.
Well that threw a spanner in the works, didn't realise type providers had this little annoying use case.
Unfortunately, yes - as far as I am aware, the dependencies need to be in a path that can be located by the provider. I tried everything I could think of, even powershell scripts to copy the DLLs to the TP folder post deploy, but it still didn't work. And Paket doesn't support powershell scripts either.
Sorry :-/
Should fix issue #51
not 100% sure if that is the right way to specify it with Fake.