Jump to content

Search the Community

Showing results for tags '.net'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Plastic SCM
    • General
    • Installation and configuration
    • Unity 3D
    • Unreal Engine
    • Plastic SCM on Mac
    • Plastic SCM on Linux
    • Gluon
    • Git interop
    • Integrations
    • Community Edition
    • Branching and merging
    • Announcements
  • Plastic SCM 4.0 Beta (Closed)
  • Plastic Cloud
    • General
    • Configuration
  • SemanticMerge
    • General
    • License
    • SCM's configuration
    • Share your experience!
    • External Parsers
  • GitJungle
  • Method History for Subversion
  • PlasticX Early Adopter Program's General Feedback
  • PlasticX Early Adopter Program's Issue Reporting
  • PlasticX Early Adopter Program's Feature Requests
  • PlasticX Early Adopter Program's Announcements

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 2 results

  1. Hello, I'm planning a completely fresh install of Plastic, no old data, migration or anything. So i thought it might make sense to take a look at the "new generation of our server, built on .NET Core and managed with systemd". It sounds like a very good step up in many areas and already being on the future version would potentially save me a difficult migration later on. I'm installing on CentOS and followed this procedure. The installation itself was overall very easy but there seem to be some things i either don't understand or are not yet working. 1. Primarily i can't get ssl to work. For the web interface this is not a big issue, i could just put a reverse proxy in front of it for that but for the client I always get an error when trying to connect: Authentication failed because the remote party has closed the transport stream. No ssl connection works fine. I tried the official procedures described here and also several other things but always get the same error. It also seems like the remoting.conf is no longer used at all? I then came along this thread claiming that it's mentioned somewhere that it's not supported yet but i could not find that information anywhere. So my first question is whether someone can confirm that ssl is not working yet and if there is an official ETA on implementing that? 2. When trying to fix ssl i also wanted to take a look at the log files but that turned out to be another issue. I can't find them. I guess because the new server is using systemd its logging is different? And logs might be in a different location but does someone know where? Or how to set logging up correctly? 3. Last but not least i wonder if there are any other limitations / missing features the new generation currently has that one should be aware of? I Just need to make an informed decision on what path to follow. Sorry for the long and overloaded post and thanks a lot in andanced for any help.
  2. I am currently coding a .NET application with TypeScript in Visual Studio 2017. When the project is built, the TypeScript files get compiled into JavaScript files. In VS, those JS files are not considered part of the project (correctly, since the TS files are the true source). How do I get PlasticSCM to ignore these files without ignoring them each individually? Thanks, Frank
×
×
  • Create New...