Forum member

iceypoi

5 posts

Posts by iceypoi

  1. Making NCRUNCH aware of additional reference (for which there is no code, just dlls)

    No, unfortunately not, I just tried again. The problem is a so called [url=http://msdn.microsoft.com/en-us/library/windows/hardware/gg463353.aspx]Session 0 isolation[/url]. In short, you can only access a GPU if you are working from Session 0 or you have a special GPU with a special Driver, e.g. [ur…

  2. Making NCRUNCH aware of additional reference (for which there is no code, just dlls)

    It has to do with the GPU driver. With the exception of some industrial GPUs (we only have like 1-2), the driver only allows you to use the GPU if you physically are logged in, no RDP, no being logged out and run as service in another user's context, etc. What does work, is accessing the computer…

  3. Making NCRUNCH aware of additional reference (for which there is no code, just dlls)

    I tried the first option and it works like a charm :-) It also feels pretty clean, given that the nuget packages does nothing with the FSharp.Data.DesignTime reference. However, I also made a trivial mini solution, that is capable of reproducing the problem https://github.com/DanielFabian/NCrunch…

  4. Making NCRUNCH aware of additional reference (for which there is no code, just dlls)

    Hi Remco, ok... so the dependencies are thus (already the production code break, but i'm pretty sure the test code will break too, since it also uses the type provider): [code=plain]FileReader (productive code) ===> FSharp.Data FileReader =/=> FSharp.Data.DesignTime FShar…

  5. Making NCRUNCH aware of additional reference (for which there is no code, just dlls)

    I have what feels like a similar issue. When using FSharp.Data (an F# type provider assembly), NCrunch fails to build, because the type provider during BUILD time has an additional dependency, namely FSharp.Data.DesignTime. A simple work-around is to actually reference the latter in my productive co…