Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    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
    not talking about UnityEngine tests... those needs Unity..
    But a simple test now, just hangs in Inconclusive
    Jurjen Biewenga
    @JurjenBiewenga
    Are you running R# at all?
    Or just plain VS?
    Flavio Engel
    @flavio.engel_gitlab
    R#
    Jurjen Biewenga
    @JurjenBiewenga
    And you're using R# to run them or the VS test tools?
    Flavio Engel
    @flavio.engel_gitlab
    R#
    Jurjen Biewenga
    @JurjenBiewenga
    I doubt this is related to Unity and rather is coincidence
    But you can try adding the nuget test runner package for nunit
    And see if that helps anything temporarily
    Otherwise it's probably best to make a bug report on youtrack
    Flavio Engel
    @flavio.engel_gitlab
    image.png
    They just stay like this when running, build show no errors, console shows no errors...
    Flavio Engel
    @flavio.engel_gitlab
    image.png
    Even creating a new Unity Project, and something as simple as
    image.png
    Jurjen Biewenga
    @JurjenBiewenga
    I suggest creating a bug report on youtrack
    Flavio Engel
    @flavio.engel_gitlab
    Will try that.
    Matt Ellis
    @citizenmatt
    Yes, best thing is to contact support directly, via youtrack or support@jetbrains.com. Not sure what's going on there, tbh.
    Flavio Engel
    @flavio.engel_gitlab
    So, in the end was such a simple thing.
    Was missing enabling the Resharper Build.
    image.png
    Samuel Truman
    @Xant3s

    Hi,

    thanks for this awesome extension!
    I recently started to use Visual Studio 2019 instead of 2017.
    However, I can't find this extension in the ReShaper extension manager.

    My setup:
    Visual Studio 2019 (16.5.2) + ReShaper 2019.3.4 (+ Unity 2019.3.7f1)

    My previous setup:
    Visual Studio 2017 (15.9.21) + ReSharper 2019.2.2

    This extension was listed in the Extension Manager on my previous setup and worked great!
    These are my registered extensionen sources on both setups:
    https://resharper-plugins.jetbrains.com/api/v2/curated-feeds/Wave_v191.0/
    https://resharper-plugins.jetbrains.com/api/v2/curated-feeds/Wave_v11.0/

    Thanks in advance!

    Matt Ellis
    @citizenmatt
    Hi! Both of those extension sources are incorrect for 2019.3. You can delete both of them, and replace with:
    https://resharper-plugins.jetbrains.com/api/v2/curated-feeds/Wave_v193.0/
    Samuel Truman
    @Xant3s
    Thank you so much! :)
    Matt Ellis
    @citizenmatt
    :thumbsup:
    Majeric
    @majeric
    I'm not entirely sure if this is an appropriate place to ask this question but my Jetbrains Rider cannot resolve symbols for my Unity project across the Editor / Runtime project assemblies
    Matt Ellis
    @citizenmatt
    Hey. Try to re-generate the project files - under the Assets menu in Unity. Or invalidate caches in Rider (File menu) and restart. And make sure that you’ve got Rider selected as the external tool in Unity.
    Jurjen Biewenga
    @JurjenBiewenga
    What's this new icon?
    Matt Ellis
    @citizenmatt
    What new icon?
    Jurjen Biewenga
    @JurjenBiewenga
    image.png
    Matt Ellis
    @citizenmatt
    Ha ha! I thought that was just a catching issue with my client!
    One of the devs added a room for the IdeaVim plugin, and that’s the icon. I’ll let him know he’s set it for the entire JetBrains organisation 😁
    Jurjen Biewenga
    @JurjenBiewenga
    :joy:
    Jurjen Biewenga
    @JurjenBiewenga
    Woo it's back
    VSMent
    @VSMent
    Hi there is anyone here?
    Ivan Shakhov
    @van800
    Yes
    Evans Thomas
    @EvansThomas
    Hello! I'm trying to build the plugin locally by running build.ps1 and it's failing with the error TestUnityAttribute.cs(96,13): error CS0246: The type or namespace name 'NugetPackagesCache' could not be found (are you missing a using directive or an assembly reference?) [C:\OtherCode\resharper-unity\resharper\resharper-unity\test\src\tests.resharper-unity.csproj]. What am I missing here?
    Matt Ellis
    @citizenmatt
    Hi! Is that on net211? There’s just been a merge of a pretty major refactoring of the base testing framework that handles restoring nuget packages to test with, which is this area. (I.e. we use nuget to restore packages that give us a consistent set of references to test against - either .net framework itself or third party assemblies such as Unity). We’ve been stuck on nuget 2 for the longest time, and it’s just been updated to a more recent version of nuget. This is likely a casuality of the rewrite.
    It’ll get fixed soon enough, but might take a day or two longer than usual due to the holiday period. In the meantime, you could use the net203 branch, which we’ve only just released as 2020.3. This will be stable, as we’re not doing active development in there right now, just maintenance fixes (and of course, the opposite is true - net211 will be less stable, especially at the start of the 2021.1 development cycle)
    Evans Thomas
    @EvansThomas
    Thank you for the quick response! I will use net203 for now.
    Evans Thomas
    @EvansThomas
    I created a plugin project using this template - https://github.com/JetBrains/resharper-rider-plugin and I'm able to run it but not debug it. Is there some information available on how I can enable debugging?
    Matt Ellis
    @citizenmatt
    Debugging C# requires attaching to the ReSharperHost process. The IDE runs as a JVM process for the UI, etc. but the C# language services are hosted in a child dotnet process. Because it’s a child process, you can’t just hit the Debug button, but have to attach to an already running instance. So hit Run to start the IDE, then attach to the dotnet hosting process (either dotnet or ReSharperHost.exe, depending on OS)
    Matt Ellis
    @citizenmatt
    net211 is compiling again, but tests don’t work. The refactoring seems to have broken something. We’ll get it fixed as soon as we can.
    Evans Thomas
    @EvansThomas
    Thank you, debugging works great! Also, I just removed the test project to get net211 to work for now.