We've moved! Join us as we continue development on our new site at umod.org!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
Thread Status:
Not open for further replies.
  1. Wulf

    Wulf Community Admin

  2. THANK YOU! i was expecting this change since release 33 on github

    im interested on git submodule because it's more easy to test it im using this git feature since 1 year and it's okay , decreased problems, modulable projects, and... the real advantage, for me

    Example ( can be ... ) :

    OxideManager
    /src/
    /modules/
    /modules/module_game_1/tests
    /modules/module_game_1/src
    /modules/module_game_2/tests
    /modules/module_game_2/src

    - Can fork main project ( that contains all submodules ) and add your own private modules working with publics
    - Can clone each project and commit
    - Can centralize Oxide.core and generate dependency

    IF you do this ILL HELP YOU to generate unitaries and functionals tests FOR ALL projects, im QA and i love to test all ^.^
     
    Last edited by a moderator: Dec 26, 2017
  3. Wulf

    Wulf Community Admin

    The projects are using NuGet for dependency management, not really interested in having to update submodules as we've had that setup in the past. Thanks for the offer though.
     
  4. Ok then, ill keep waiting for changes to start BDD with your projects , but i love space engineers , theForest , Rust


    expecting code changes....
     
  5. Hi, I tried to fork one of Oxide project repository but i'm kind of lost when I have to run the powershell script.
    It asked for 3 arguments, project, dotnet and managed and i'm not sure of what should I put here.
    I tried to put "Rust" or "Oxide.Rust" in project (I have forked Oxide.Rust) but even with that, it say that the script couldn't find a .csproj for this game.
    Can you help me for this part ?
    Thanks.
     
  6. Wulf

    Wulf Community Admin

    Open the .sln in Visual Studio and build it as you normally would. In this case, Oxide.Rust.sln. The PowerShell script isn't intended to be ran manually, it's used by the .csproj.
     
  7. For me, it's down this code now, api changed?

    Code:
    wget https://api.github.com/repos/OxideMod/Oxide.Rust/releases/latest --no-check-certificate
    --2018-02-25 03:19:26--  https://api.github.com/repos/OxideMod/Oxide.Rust/releases/latest
    Resolving api.github.com... 192.30.253.117, 192.30.253.116
    Connecting to api.github.com|192.30.253.117|:443... connected.
    OpenSSL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
    Unable to establish SSL connection.
    edit: ok, wget need to be updated: GNU Wget 1.19.4 for Windows
     

  8. Get the latest wget.exe from here --> eternallybored.org/misc/wget/ ;)
     
    ☺ Tanki ☺ likes this.
  9. Gettin the same problem even with the latest Wget, dont think thats the only issue, seems more like the links requirements now :/

    Code:
    Invoke-WebRequest : The request was aborted: Could not create SSL/TLS secure channel.
    At D:\Server_Management\Update\Oxide.ps1:1 char:9
    + $json = Invoke-WebRequest -Uri "https://api.github.com/repos/OxideMod ...
    +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        + CategoryInfo          : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-WebRequest], WebExc
       eption
        + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeWebRequestCommand
    
    --2018-02-26 06:27:32--  https://github.com/OxideMod/Oxide.Rust/releases/download//Oxide.Rust.zip
    Resolving github.com (github.com)... 192.30.253.113, 192.30.253.112
    Connecting to github.com (github.com)|192.30.253.113|:443... connected.
    HTTP request sent, awaiting response... 404 Not Found
    2018-02-26 06:27:32 ERROR 404: Not Found.
     
    Last edited by a moderator: Feb 26, 2018
  10. Dude. Did you ever tryied to google the error itself?
    You are using the ps script made by Wulf and edited by me, as I see.
    You have to add
    Code:
    [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
    to the top of the script.
     
  11. Done, thanks a million :)
     
  12. dude, just... google the problem first =)
    I'm just tired of googling things for overs =_=
     
  13. Alright calm your tits
     
Thread Status:
Not open for further replies.