Autocompletion wants me to build the project #123
Comments
|
I was having a similar issue and fixed it by following the trouble shooting in item two of this disucssion. To save you a click; Close VSCode, navigate to project folder in terminal, call |
I mentioned in my initial comment above that building the project does not help. Reopening VSCode or Neovim after also doesn't work. I think the LSP fails to detect that the project has been built. |
|
I had the same issue here. What helped me was to install the following two extensions in vscode:
After that autocomplete started to work. |
I wonder what the equivalent fix is in Neovim, as I don't actually use VSCode for any development. |
|
Tried to do the same thing... vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {
pattern={"*.axaml"},
group=vim.api.nvim_create_augroup("axaml-ls", { clear = true } ),
callback = function()
local lsp_bin_dir = "~/.vscode/extensions/avaloniateam.vscode-avalonia-0.0.31/avaloniaServer/"
local lsp_bin_path = "~/.vscode/extensions/avaloniateam.vscode-avalonia-0.0.31/avaloniaServer/AvaloniaLanguageServer.dll";
if vim.fn.isdirectory(lsp_bin_dir) then
vim.cmd.setfiletype("xml")
vim.lsp.start({
name = "axaml",
cmd = {"dotnet", lsp_bin_path, "--stdio"},
root_dir = vim.fn.getcwd(),
capabilities = capabilities,
})
else
print("Failed to start Avalona Language Server because the lsp bin dir is incorrect!")
end
end
})And it doesnt work however I managed to fix it in vscode.. It seems that the LSP or maybe the extension I am unsure.. But it seems to be asking the .Net Install Extension in vscode to install dotnet 8 and probably something else who knows I fixed it in vscode by giving my dotnet bin path to .Net Install. I pretty much opened up "User profile settings (JSON)" |
I tried in VSCode and gave the .NET path. It still didn't work though. And even if it did it wouldn't help me since I never use VSCode. |
|
Heres what I did to fix it for vscode.. Sadly I want to use Neovim but I cant seem to get it too work. Step 1Open up settings.json.. Ctrl + Shift + p Step 2Add the following to your settings.json }
"dotnetAcquisitionExtension.existingDotnetPath": [
{"extensionId": "AvaloniaTeam.vscode-avalonia", "path": "/usr/bin/dotnet"}
],
"dotnetAcquisitionExtension.installTimeoutValue": 180,
"editor.minimap.enabled": false
}REPLACE /usr/bin/dotnet WITH THE BIN PATH TO DOTNET In order to find the dotnet bin path open up the terminal and run |
|
Now I wonder how you can replicate this in Neovim. If I didn't use Neovim I'd use Rider instead of VSCode, which has official Avalonia support. |
|
I made it work once but then I did something by mistake and it broke.. I tried remaking it and even moving the LSP. vim.api.nvim_create_autocmd({"BufNewFile", "BufRead"}, {
pattern={"*.axaml"},
group=vim.api.nvim_create_augroup("axaml-ls", { clear = true } ),
callback = function()
if vim.fn.isdirectory("~/.config/nvim/LSP-Servers/") then
local lsp_bin_dir = "~/.config/nvim/LSP-Servers/avaloniaServer"
local lsp_bin_path = "~/.config/nvim/LSP-Servers/avaloniaServer/AvaloniaLanguageServer.dll";
if vim.fn.isdirectory(lsp_bin_dir) then
vim.cmd.setfiletype("xml")
vim.lsp.start({
name = "axaml",
cmd = {"dotnet", lsp_bin_path},
root_dir = vim.fn.getcwd(),
capabilities = capabilities,
})
else
print("Failed to start Avalona Language Server because the lsp bin dir does not exist!")
end
else
print("Failed to start Avalonia Language Server. LSP-Servers directory does not exist!")
end
end
})But sadly it just responds with something like "Client 1 exit with 1 and quit with 0" |
|
Well I guess some how someone made it work.. |
That one is only for previewer, as far as I can see. |
|
It shows a example for LSP. |
|
I messed around a bit and managed to get some of the LSP to work now the LSP just keeps recommending the same completion according to the LSP logs. local Avalonia_LSP_Path_dir = vim.fn.expand("~/.config/nvim/LSP/avaloniaServer/")
local Avalonia_LSP_Path = vim.fn.expand("~/.config/nvim/LSP/avaloniaServer/AvaloniaLanguageServer.dll")
function _ISFILE(name, root)
if type(name) ~= "string" then
return false
end
if type(root) ~= "string" then
return false
end
return vim.fn.findfile(name, root)
end
vim.api.nvim_create_autocmd({ "BufNewFile", "BufRead" }, {
pattern = { "*.axaml" },
group = vim.api.nvim_create_augroup("Avalonia_LSP", { clear = true }),
callback = function()
if vim.fn.isdirectory(Avalonia_LSP_Path_dir) then
if not _ISFILE("AvaloniaLanguageServer.dll", Avalonia_LSP_Path_dir) then
print("Avalonia LSP does not exist!")
return
end
vim.cmd.setfiletype("xml")
-- Setting the root_dir
local root_dir = lspconfig.util.root_pattern("*.csproj", "*.sln")(vim.fn.getcwd())
if not root_dir then
print("Root directory not found!")
return
end
-- For debugging
print("Root directory: " .. root_dir)
-- Building the project
print("Building the project!")
vim.cmd("!dotnet build")
vim.lsp.start({
name = "Avalonia_LS",
cmd = { "dotnet", Avalonia_LSP_Path },
root_dir = root_dir,
filetypes = { "axaml", "xml" },
capabilities = capabilities, -- Your capabilities
})
-- For debugging
vim.lsp.set_log_level("debug")
local log_path = vim.lsp.get_log_path()
print("LSP log path: " .. log_path)
else
print("Avalonia LSP Dir not found!.. Provided path: " + Avalonia_LSP_Path_dir)
end
end,
})
vim.api.nvim_create_user_command("BuildProject", function()
vim.cmd("!dotnet build")
end, {})
|
Fix!Open up vscode and when it asks you to Build the project just press enter and let it do it's thing after that close vscode and open up neovim with your avalonia LSP config and it should work! |
|
I found out that the Avalonia LSP requires some files in the Bin and OBJ directories. So its able to create those files in VScode but it is not able to in Neovim so what you can do is create a template that already contains the files required for the LSP and each time you use Avalonia instead of doing dotnet new avalonia.app you can just do git clone https://user/my-template. The template should contain the right files for the LSP to work correctly! This can be easily fixed in neovim now let me try explaining how it should work in neovim! So what you can do is every time the Avalonia LSP Attaches and there's a axaml file you can use LUA to create the required files for the avalonia LSP meaning the user or you will never have to tab into vscode just to build the project! How I found this out??I started by creating a avalonia app and then tracking files being created & deleted I found out that some files were modified and new files were created after the vscode extension attempted to build the project.. I managed to get it working in neovim!!!! |
|
Selecting 'Build the project' in VSCode and pressing Enter did not work for me. But then I noticed that it runs the build command with EDIT: Nevermind, turns of the version of the extension I installed in VSCode was not uploaded by the Avalonia team, and was an older version (0.0.26). |
|
I mean you can just create a bash script to create the files that it requires.. But who in the world has enough time to figure all of that out? its been 3 weeks and I haven't tested it and to be honest if it's this annoying to get a LSP to work then I might aswell just use GTK4. |
|
Just came across this issue. I am using VSCode and .NET 8.0.400-preview.0.24324.5 and believe that my fix will only be applicable for those using a preview version. TL;DRIdentified and fixed issues with the Detailed DescriptionIssues Addressed by the Fix
FixUpon reviewing the logs, I identified the following entries: The entry for {
"solution": "../[SolutionName].sln",
"projects": [],
"files": []
}This content was clearly incorrect. To address this, I executed the following command: dotnet "...\.vscode-insiders\extensions\avaloniateam.vscode-avalonia-0.0.31\solutionParserTool\SolutionParser.dll" "...\[SolutionName].sln"The result was an error: Error parsing project [ProjectName]: Invalid static method invocation syntax: "[MSBuild]::SubstringByAsciiChars($(MSBuildProjectFile), 0, 8)". Method '[MSBuild]::SubstringByAsciiChars' not found. Static method invocation should be of the form: $([FullTypeName]::Method()), e.g. $([System.IO.Path]::Combine(`a`, `b`)). Check that all parameters are defined, are of the correct type, and are specified in the right order. ...\dotnet\sdk\8.0.400-preview.0.24324.5\Microsoft.Common.CurrentVersion.targetsUpon examining the <MSBuildCopyMarkerName Condition="'$(MSBuildCopyMarkerName.Length)' > '17'">$([MSBuild]::SubstringByAsciiChars($(MSBuildProjectFile), 0, 8)).$([MSBuild]::StableStringHash($(MSBuildProjectFile)).ToString("X8"))</MSBuildCopyMarkerName>I compared this with the version -<MSBuildCopyMarkerName Condition="'$(MSBuildCopyMarkerName.Length)' > '17'">$(MSBuildProjectFile.Substring(0,8)).$([MSBuild]::StableStringHash($(MSBuildProjectFile)).ToString("X8"))</MSBuildCopyMarkerName>
+<MSBuildCopyMarkerName Condition="'$(MSBuildCopyMarkerName.Length)' > '17'">$([MSBuild]::SubstringByAsciiChars($(MSBuildProjectFile), 0, 8)).$([MSBuild]::StableStringHash($(MSBuildProjectFile)).ToString("X8"))</MSBuildCopyMarkerName>As seen, there was a change. I then examined the code to determine which library was used for project information collection, which was By copying the .NET preview |
|
Yay |
Describe the bug
When I try to use autocomplete in VSCode in a .axaml file the only option that shows up is "Build the project". Building the project does not help. I am actually using Neovim with the LSP, but I tried it in VSCode as well, and the issue persists.
To Reproduce
The project consists of a root folder with an
.slnfile and 4 other folders containing.csprojfiles. One of the folders contains an Avalonia project. This is the project I am trying to use the extension with: BachelorProjectAvalonia for VS Code
v0.0.26
Avalonia version
v11.0.10 and tested v11.0.2 as well
VS Code version
v1.88.1
Relevant log output
Additional context
In Neovim I used the following to set up the LSP:
P.S. In the log output I can see that it runs with
--sdk 7.0. Does this mean I cannot use .NET 8.0 and have to use .NET 7.0?The text was updated successfully, but these errors were encountered: