AvaloniaLSP looks for assemblies in obj/Debug
, but it should be looking in obj/Debug/$(TFM)/
#84
Labels
obj/Debug
, but it should be looking in obj/Debug/$(TFM)/
#84
Describe the bug
AvaloniaVSCode/src/AvaloniaLSP/AvaloniaLanguageServer/Models/Workspace.cs
Lines 49 to 52 in c0bb008
https://github.com/AvaloniaUI/AvaloniaVS/blob/4190a20de1cfa27324d82c1258ad6d03540ec98f/CompletionEngine/Avalonia.Ide.CompletionEngine/AssemblyMetadata/AvaloniaCompilationAssemblyProvider.cs#L11-L33
For a multi-targeting project,
dotnet publish
requires the--framework $TFM
argument. However,dotnet build
will build the project for each target framework specified via theTargetFrameworks
project property.Regardless, single-target projects will output intermediate files to per-framework sub-folders.
To Reproduce
Start debugging the extension, create a new Avalonia App in the extension development host, open an axaml file, check logs.
If this doesn't reproduce the issue, I will have time to rectify it on Saturday.
Avalonia for VS Code
v0.0.25
Avalonia version
v11.0.4
VS Code version
v1.85.1
Relevant log output
Additional context
I found this while debugging
createPreviewerAssets.ts
and its dependency files.The text was updated successfully, but these errors were encountered: