Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    btrepp
    @btrepp
    My project being on netfx, no worries argu is there. Change it to netcoreapp2.1 and everything else appears in references but argu.
    Seems to occur when I change it to netstandard20 aswell, that's bizarre
    btrepp
    @btrepp
    Ah i'm going to assume that having groups was the issue. I seperated my mixed apps into having two very independent groups and argu appeared again
    Sandeep Chandra
    @sandeepc24

    I have a solution with multiple projects and the paket.references file has various groups. I want to add a dependency to a project using a Paket group and I run paket.exe add Hopac -g Server. It looks like the reference is added to the project's reference file but the app fails to build complaining that the namespace in the package was not found.

    I am still not very clear about how groups work, could someone shed some light on what I am doing wrong?

    Onur Gumus
    @OnurGumus
    @sandeepc24 it should work.
    as is.
    try to simplify it.
    PinkyBrain
    @PinkyBrain_gitlab
    how come my paket.restore.targets file changes by itself in vs code?
    is this the ionide extension doing something in the background? it's a bit invasive... makes life difficult when doing git housekeeping
    Dustin Lacewell
    @dustinlacewell
    I am trying to run paket install with a git package utilizing the Packages: keyword. When I run it locally, the Packages: keyword path is relative to the Solution root. When I run it from inside Docker, the path is relative to the Project root. What gives...?
    Frank Behrens
    @fbehrens

    when i do

    #paket.dependencies
    framework: net461
    redirects: on
    source https://nuget.org/api/v2
    nuget FSharp.Core redirects: force
    ...
    
    .paket\paket.exe install --generate-load-scripts --load-script-framework net461 --load-script-type fsx

    the generated main.group.fsx references Java.Interop,Mono.Android,System.Windows.Browser,Xamarin.iOS, which are not on my win10.
    My current workaround is to uncomment manually in generated loadfile.
    How to make it right ?

    Dustin Lacewell
    @dustinlacewell
    Is Paket dead?
    Dustin Lacewell
    @dustinlacewell
    Signs pointing to "yes".
    Steffen Forkmann
    @forki
    Not dead. Just vacation time
    Dustin Lacewell
    @dustinlacewell
    @forki Paket's refusal to use local git repositories with unstaged changes is absolutely killing me
    Dustin Lacewell
    @dustinlacewell
    The latest Nuget has a -Deterministic flag. Please make a release of Paket that uses this new version of Nuget so that I can produce packages for use on pure systems like NixOS
    dustinlacewell @dustinlacewell said into the void.
    btrepp
    @btrepp
    Is it insane to potentially use the external_lock sub command as something like a package set (eg like haskells stack?). I'd like to have a curated set for our internal apps, maybe with a build server constantly updating the package set
    Steffen Forkmann
    @forki
    @dustinlacewell please open an issue with details
    beatcracker
    @beatcracker
    Hi folks! Quick question: is there any way to mimic nuget install command? Because packet add modifies paket.dependencies, while I'd like to just download a package w/o adding it anywhere. This is for CI/CD usage, no projects involved.
    beatcracker
    @beatcracker
    Repo level tools look promising: fsprojects/Paket#2919
    Yaroslav Veremenko
    @veremenko-y
    Hi! Can someone help me out? I'm messing up with trying to install asp.net core on net47. But when I add nuget Microsoft.AspNetCore.All 2.2.7 to the dependencies, nothing gets installed in the project references. Any idea why that would happen?
    Sergey Tihon
    @sergey-tihon
    @veremenko-y do you have paket.references file near the project file? https://fsprojects.github.io/Paket/img/paket-overview.png
    Yaroslav Veremenko
    @veremenko-y
    Yes I do. It is actually working file. It is Microsoft.AspNetCore.All or Microsoft.AspNetCore.App packages specifically that do not update the project file. Anything else is working fine
    btrepp
    @btrepp
    is there anything special to get azure devops to build using paket? dotnet restore's calling paket okay, but the build process gets 401'd with it's own artifact feed
    - task: DotNetCoreCLI@2
      displayName: 'Restore'
      inputs: 
        command: restore
    This task seems to say it creates a 'temporary nuget.config which maybe does the credential-fu?, but it doesn't seem to get passed down to paket correctly.
    szrn
    @szrn

    a package that i am referencing contains a .targets project that is getting transitively included via paket.restore.targets, but i need to prevent that so i can customize the work being done in that target. anyone know how to do that?

    this sorta sounds like disabling auto-restore for a specific project, but i actually want all the other paket auto-restore functionality -- i just want to prevent the inclusion targets from dependencies.

    anyone know how to do this?

    nawfalhasan
    @nawfalhasan
    I find dependency resolution algorithm to be a lot better with packagereference approach of nuget. It would be sensible to update the paket FAQ to include packagereference
    nawfalhasan
    @nawfalhasan
    Is there a simple writeup about paket's dependency conflict resolution algorithm? Something like this https://docs.microsoft.com/en-us/nuget/concepts/dependency-resolution for nuget's. I find https://fsprojects.github.io/Paket/resolver.html extremely technical and difficult to follow
    btrepp
    @btrepp

    is there anything special to get azure devops to build using paket? dotnet restore's calling paket okay, but the build process gets 401'd with it's own artifact feed

    Through googling I figured out I need to auth with the feed, there is a devops helper for this :)

    Steffen Forkmann
    @forki
    erikljung
    @erikljung

    Hi, trying to figure out if there is a way to keep third party dependencies "sealed" within a project. There might be a possibility that I don't understand dependency chain of net core, but then I will learn something.
    Example

    • ProjectA have a project reference on ProjectB
    • ProjectB have a reference on third party lib Npgsql to implement a connection string builder, lets call it ClassX.GetConnectionString()
    • ProjectA will use ProjectB ClassX to resolve connection strings

    What I would like to achieve is that ProjectA should know nothing about Npgsql but
    still be able to use ClassX.GetConnectionString().

    Is this possible to achieve?

    Matthias Dittrich
    @matthid
    @erikljung What does "know nothing" mean? The compiler should not emit a static dependency as long as no types are directly required but at runtime the dependency will be required obviously
    erikljung
    @erikljung
    @matthid Thanks for your time. I've would like Npgsql to be inaccessible at design time (more or less no intellisense), in order to prohibit devs to directly access Npgsql in ProjectA.
    Matthias Dittrich
    @matthid
    I think you can do this only with analyzers or check afterwards and fail the build (which should be surprisingly easy to do actually)
    erikljung
    @erikljung
    That seems like a solution. So I guess according to you, there is no "native way" to "hide" third party dependencies when referencing a project?
    Matthias Dittrich
    @matthid
    At least I'm not aware of a feature like that. Usually you want the reverse or at least are fine with the current behavior
    erikljung
    @erikljung
    (I understand that this is not really a question about Paket, but I thought it would end up in some configuration for Paket, so I'm grateful for you helping me)
    Ok ok
    Well, I've been looking for an answer to this question, unable to find one, so I think your answer is as good as it gets :).. Thanks again.
    kerams
    @kerams

    Hi. I'm using https://www.nuget.org/packages/Serilog.Sinks.Console/3.1.2-dev-00824 in a netcoreapp3.0 project and even though that prerelease version should only depend on Serilog (for netstandard2.0), the lock file contains this:

    serilog.sinks.console (3.1.2-dev-00824)
          Serilog (>= 2.8)
          System.Console (>= 4.3)
          System.Runtime.InteropServices (>= 4.3)
          System.Runtime.InteropServices.RuntimeInformation (>= 4.3)

    which looks exactly like .NETCoreApp 1.1 dependencies listed on Nuget.org. What am I missing here?

    David Cumps
    @CumpsD
    quick question, the new .net core 3 local tools, can you manage them with paket.dependencies too? or just .config? or will the old clitool write that out?
    Matthias Dittrich
    @matthid
    @CumpsD paket doesn't even support global tools...
    David Cumps
    @CumpsD
    oh
    Matthias Dittrich
    @matthid
    But PR is welcome ;)
    David Cumps
    @CumpsD
    first the PR for fake :p lol that one will take a bit already
    just have to remember I will have to manage versions in 2 spots
    .config as well
    erikljung
    @erikljung
    Hi, do you guys have any good pointers on how to work with Paket and Docker (C# .net core)? In my case I'm trying to use some build server (AWS CodeBuild or Bitbucket pipelines) to run tests, but since we have fsprojects/Paket#2660 how do you guys work around this? Is there any good Docker images/examples that you can point me to? (Im fairly new to both Paket and Docker).
    Yoann
    @arthis
    Not sure if this is the best place to ask, you 'll tell me. I was wondering if there were any plans to uncouple the resolution of dependencies from the fetching of packages? I am looking to implement a paket like application to manage micro services, the way paket manages packages. Is there anyone around here that has begun such an adventure? I will gladly give any explanations. I am rather thinking about the project than implementing it at the moment.