search

eclipse / aCute

Eclipse aCute - C# edition in Eclipse IDE
https://projects.eclipse.org/projects/tools.acute
Eclipse Public License 2.0
80 stars 33 forks source link

After creating a new .NET CORE Project getting the "Building Workspace" Error #136

Open premanir opened 6 years ago

premanir commented 6 years ago

I have created my first .NET CORE project using Eclipse as IDE and installed acute plugin and added the .NET CORE preferences Then created a new .NET CORE project I have encountered the below error Please help me to resolve the issue

image

mickaelistria commented 6 years ago

Can you check in Window > Preferences > .NET Core whether the pat to the dotnet executable is correct?

premanir commented 6 years ago

I think it is correct, then only the "Apply and Close" button will get enable.

Please find the below screenshot for reference

image

LucasBullen commented 6 years ago

Do you continuously get this error message or just for the first time the workspace builds after the project creation?

premanir commented 6 years ago

This is my first C# project in Eclipse Earlier for past 3 years I am working on Eclipse using Java and never experience such error before This error I came across for the first time only while building a C# workspace and the information available online is also scarce for this respective configuration

LucasBullen commented 6 years ago

I created a PR that will hopefully solve this issue. However, since I am unable to reproduce it, I can not be 100% sure. If the problem persists or the error warning is irritating you in the mean time, you are able to remove the builder from the project so that the fault won't happen:

Right click on the project in the Package Explorer > Configure > Remove .NET Builder

mickaelistria commented 6 years ago

From the screenshot and "Connot run program dotnet", I have the impression it can be that the builder doesn't resolve well to the path where dotnet is installed and configured in preferences.

premanir commented 6 years ago

@LucasBullen @mickaelistria I have removed the .NET builder following the exact navigation Then I removed the complete project itself from the workspace Then I again created a new . net project and i did not encountered any error The project got created successfully But I am not able to use the predefined functions which are suggested to the user by displaying in a drop down Please find the below screenshot image

mickaelistria commented 6 years ago

Can you share interesting part of you eclipse-workspace/.metadata/.log file?

premanir commented 6 years ago

.log.log

mickaelistria commented 6 years ago

Thanks. Log shows a lot of Server file not found. Has Omnisharp server been unpacked in C:\Users\rpremani\eclipse-workspace\.metadata\.plugins\org.eclipse.acute\omnisharp-roslyn ? Can you please check wheter thiere is something in the specified directory or in a sibling?

premanir commented 6 years ago

omnisharp-roslyn.zip I can see all the dll files in omnisharp-roslyn folder

sign-in-smth commented 5 years ago

(a) i keep getting the "Building Workspace" freeze occasionally (except for the very first time after eclipse restart). (b) java.lang.NullPointerException in Outline tab most of the time. (c) also many "omnisharp" errors in log. (d) overall, editing code feels laggy/slow, ex. if i try to replace or paste text.

i tried both stable acute version and then latest from snapshots, same results. i have .net core 2.1.502 and dotnet.exe location specified in eclipse settings as instructed.

steps to reproduce the building workspace freeze: -create new .net core project with default settings (console application c#); -paste this attached other hello world code (took it from a .net framework tutorial); -create a run configuration with default settings; -run it, code will compile fine and output to console; -clear console, change int a=1 to int a=2, save code; -try to run it and you get the building workspace error; -restart eclipse, run the same code, it will work fine; -repeat an edit (like change 2 back to 1) and you get the freeze again... -plus the other (b), (c), (d) as mentioned above

PS: if the code itself is not correct for .net core test, you let me know guys, i'm new to this.

log: .log code: hello world.txt

mickaelistria commented 5 years ago

I hope this improves when omnisharp 1.32.9 or 1.33.0 is released and we can switch to it.

sign-in-smth commented 5 years ago

thanks, will be looking forward to it!

about (a), pls disregard it: after a little closer look i saw that new build (after code editing) hangs just because previous launch hasn't terminated. that sneaky readline at the end waiting for input.. my bad sorry-)