uno: XAML / C# hot reload does not work on debian linux

Current behavior

When starting an app, the error messages appears:

fail: Uno.UI.RemoteControl.RemoteControlClient[0] Failed to get remote control server port from the IDE for endpoint 192.168.34.190. fail: Uno.UI.RemoteControl.RemoteControlClient[0] Failed to get remote control server port from the IDE for endpoint 192.168.1.108. fail: Uno.UI.RemoteControl.RemoteControlClient[0] Failed to get remote control server port from the IDE for endpoint 192.168.100.1. fail: Uno.UI.RemoteControl.RemoteControlClient[0] Failed to get any remote control server endpoint from the IDE.

Expected behavior

XAML and C# hot reload should work

How to reproduce it (as minimally and precisely as possible)

dotnet new unoapp -sw:false -mobile:false -slf:false -vs -s -wpm -ho -f:net7.0 Run vscode Hit F5

Workaround

No response

Works on UWP/WinUI

None

Environment

Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="5.0.0" />
    <PackageReference Include="Uno.Core.Extensions.Logging.Singleton" Version="4.0.1" />
    <PackageReference Include="Uno.WinUI" Version="4.7.56" />
  </ItemGroup>
  <ItemGroup Condition="'$(TargetFramework)'=='net7.0-windows10.0.18362'">
    <PackageReference Include="Microsoft.WindowsAppSDK" Version="1.1.3" />
    <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" RuntimeFrameworkVersion="10.0.22000.24" />
    <FrameworkReference Update="Microsoft.Windows.SDK.NET.Ref" TargetingPackVersion="10.0.22000.24" />
  </ItemGroup>

And

  <ItemGroup>
    <PackageReference Include="Microsoft.Extensions.Logging.Console" Version="5.0.0" />
    <PackageReference Include="Uno.WinUI.Skia.Gtk" Version="4.7.56" />
    <PackageReference Include="Uno.WinUI.RemoteControl" Version="4.7.56" Condition="'$(Configuration)'=='Debug'" />
    <PackageReference Include="Uno.UI.Adapter.Microsoft.Extensions.Logging" Version="4.7.56" />
    <PackageReference Include="Uno.WinUI.Lottie" Version="4.7.56" />
    <PackageReference Include="SkiaSharp.Views.Uno.WinUI" Version="2.88.3" />
    <PackageReference Include="SkiaSharp.Skottie" Version="2.88.3" />
  </ItemGroup>

And

  <ItemGroup>
    <PackageReference Include="Microsoft.Extensions.Logging" Version="6.0.0" />
    <PackageReference Include="Microsoft.Windows.Compatibility" Version="6.0.0" />
    <PackageReference Include="Uno.Extensions.Logging.WebAssembly.Console" Version="1.4.0" />
    <PackageReference Include="Uno.WinUI.WebAssembly" Version="4.7.56" />
    <PackageReference Include="Uno.WinUI.RemoteControl" Version="4.7.56" Condition="'$(Configuration)'=='Debug'" />
    <PackageReference Include="Uno.UI.Adapter.Microsoft.Extensions.Logging" Version="4.7.56" />
    <PackageReference Include="Uno.Wasm.Bootstrap" Version="7.0.11" />
    <PackageReference Include="Uno.Wasm.Bootstrap.DevServer" Version="7.0.11" />
    <PackageReference Include="Uno.WinUI.Lottie" Version="4.7.56" />
  </ItemGroup>

Affected platforms

WebAssembly, Skia (GTK on Linux/macOS/Windows)

IDE

Visual Studio Code

IDE version

1.86.1

Relevant plugins

C# v2.18.15 (pre-release) C# Dev Kit v1.3.10 Uno Platform v0.12.0

Anything else we need to know?

The launch json fragment:

    {
      // Use IntelliSense to find out which attributes exist for C# debugging
      // Use hover for the description of the existing attributes
      // For further information visit https://github.com/OmniSharp/omnisharp-vscode/blob/master/debugger-launchjson.md
      "name": "Debug (Chrome, WebAssembly)",
      "type": "msedge",
      "request": "launch",
      "url": "http://localhost:5000",
      "webRoot": "${workspaceFolder}/Project.Wasm",
      "inspectUri": "{wsProtocol}://{url.hostname}:{url.port}/_framework/debug/ws-proxy?browser={browserInspectUri}",
      "timeout": 30000,
      "server": {
        "runtimeExecutable": "dotnet",
        "program": "run",
        "outputCapture": "std",
        "timeout": 30000,
        "cwd": "${workspaceFolder}/Project.Wasm"
      }
    },

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 19 (8 by maintainers)

Most upvoted comments

Thanks! For the template errors, in theory, uno.check is supposed to fix this, but it looks like it should also be uninstalling the legacy versions of the templates. Good feedback!

Thanks for the inodes change, we’ll make some modifications to our extensions.