Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Matt Ellis
    @citizenmatt
    I’ll add more to the issue
    Jurjen Biewenga
    @JurjenBiewenga
    Alright, thanks!
    Jurjen Biewenga
    @JurjenBiewenga
    Hey! Just popping in to see whether someone has had time to check out my update to #1167
    Adavidoaiei Dumitru-Cornel
    @adavidoaiei
    Hello, for ide rider is it a channel?
    Matt Ellis
    @citizenmatt
    Hey. Sure, the Unity support in this repo is for both Rider and ReSharper.
    Adavidoaiei Dumitru-Cornel
    @adavidoaiei
    OK, thanks, I will keep looking on your channel
    Jurjen Biewenga
    @JurjenBiewenga
    Hey, I got a new laptop and installed Rider again and tried opening the Resharper-Unity project and I'm getting a whole bunch of Microsoft.DOT.netSDK missing errors. How can I fix this?
    Matt Ellis
    @citizenmatt
    Have you installed .net core?
    Jurjen Biewenga
    @JurjenBiewenga
    Yeah
    Matt Ellis
    @citizenmatt
    What msbuild do you have selected in Toolsets and Build?
    Also, run ./build.ps1/.sh first
    Jurjen Biewenga
    @JurjenBiewenga
    I've ran build.ps1
    And I've tried every msbuild in toolsets and build
    I also downlaoded the jetbrains fork of msbuild
    And that kind of worked except for the gradle launcher
    Matt Ellis
    @citizenmatt
    And it all builds ok from the shell scripts? That does suggest that Rider isn’t using the same msbuild as the scripts. Are you are Windows or Mac?
    Jurjen Biewenga
    @JurjenBiewenga
    Yeah I think it runs from fine from the shell scripts, I'd double check but I'm at work
    I'm on windows
    Jurjen Biewenga
    @JurjenBiewenga
    The shell scripts do work
    Matt Ellis
    @citizenmatt
    Did you get things working? (Been on vacation)
    Jurjen Biewenga
    @JurjenBiewenga
    Nope
    Been on vacation as well :P
    Matt Ellis
    @citizenmatt
    Make sure you’ve installed the .net core SDK, not just the runtime
    Jurjen Biewenga
    @JurjenBiewenga
    Oh yeah I have, I forgot about this
    Matt Ellis
    @citizenmatt
    Heh. Is this still a thing? Shall we just leave it until next week when we’re both in Copenhagen? :)
    Jurjen Biewenga
    @JurjenBiewenga
    Haha sure
    I haven't actually tried again
    Matt Ellis
    @citizenmatt
    Bring your laptop, we’ll get it working :)
    Jurjen Biewenga
    @JurjenBiewenga
    Sure thing
    I'd probably just have to install VS
    lingongames-mikael
    @lingongames-mikael

    Hey! I've got a bit of a weird issue and I'm stumped as to how to fix it:

    I'm using Unity 2018.4.3 and Rider 2019.1.3. In my project, I have Firebase integrated. Firebase uses https://github.com/parse-community/Parse-SDK-dotNET to add newer .NET functionality (like Tasks) to older .NET standards. Somehow, Firebase's SDK takes care of the naming clashes when using the .NET 4.x scripting runtime, as I am in Unity 2018.4.3.

    In Unity the project compiles nicely, but in Rider I get an error when awaiting FirebaseApp.CheckAndFixDependenciesAsync (a method returning Task<Firebase.DependencyStatus> (extra sidenote: the Task class returned is from within Parse-SDK-dotNET, not the standard .NET runtime)):
    'Type 'System.Threading.Tasks.Task<Firebase.DependencyStatus>' is not awaitable.'

    The code functions as it's supposed to, so it seems like Rider doesn't understand what's going on between the different assemblies. If I try the stripped down code:

    public Task<DependencyStatus> InitFirebaseAsync()
    {
        return FirebaseApp.CheckAndFixDependenciesAsync();
    }

    I get the error:
    Cannot convert expression type 'System.Threading.Tasks.Task<Firebase.DependencyStatus> [Firebase.App, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]' to return type 'System.Threading.Tasks.Task<Firebase.DependencyStatus> [netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51]'

    Which points to a clash between the two assemblies. How can I get Rider to figure out the difference?

    Thanks in advance!

    Ivan Shakhov
    @van800
    Does it compile in Unity? Does it compile in Rider?
    lingongames-mikael
    @lingongames-mikael
    It compiles in Unity and I can create builds. In Rider is listed as an error in solution.
    'Build Solution' in Rider does not give any errors.
    Ivan Shakhov
    @van800
    Have you tried Build-Build Solution in Rider?
    I see.
    Please try File-Invalidate caches and restart
    lingongames-mikael
    @lingongames-mikael
    Nope, still gives me the error.
    Ivan Shakhov
    @van800
    It may also well be already fixed in newest Rider release.
    You can use https://www.jetbrains.com/toolbox-app/
    and install newest Rider release/EAP and see if the issue was already solved.
    Toolbox allows easily to have several versions of Rider side by side.
    lingongames-mikael
    @lingongames-mikael
    I'll check that out, thanks!
    lingongames-mikael
    @lingongames-mikael
    Yay, it seems like the issue is fixed in 2019.3 EAP at least! I'm glad I didn't fall for the "have you tried turning it off and on again" trap, but didn't realize to try updating... :palm_tree:
    thanks for helping me out
    Flavio Engel
    @flavio.engel_gitlab

    Hey all...

    I need some help, we recently updated our project to Unity 2018 LTS (.net still 3.5) and now our unit test does not run on VisualStudio 2019. (Rider is fine)

    Any tips on how to solve this issue ?

    Jurjen Biewenga
    @JurjenBiewenga
    Have you tried updating VSTU?
    Matt Ellis
    @citizenmatt
    Tests won't run in Visual Studio, even if you're using ReSharper. Unity tests need to run in the Unity process, or the native part of the API isn't available. Rider supports this, but ReSharper doesn't, and neither does VS
    Flavio Engel
    @flavio.engel_gitlab
    Matts, not really our unit tests always ran on IDE. Only after updating to 2018LTS, stoped.
    I'll double check if VSTU is up to date.
    Jurjen Biewenga
    @JurjenBiewenga
    What kind of tests are you running?
    Flavio Engel
    @flavio.engel_gitlab
    plain C# class tests