Add Import->Other->NET Core->.NET Core Project

[nimo23]

When importing an existing dotnet project into eclipse, the dotnet project has a reference to the JRE System Library - Eclipse does not know that this is NOT a java project. Would be nice to include the dotnet System Library (as a reference) instead.

Maybe aCute can be enhanced by adding a dedicated Eclipse Project Facet which can be also enabled by Eclipse-Project-Menu->Configure->Add dotnet Nature (or Add dotnet Capabilities)

[mickaelistria]

When importing an existing dotnet project into eclipse, the dotnet project has a reference to the JRE System Library

That is not expected. Does the project also contain some .java or pom.xml file that would make Eclipse guess it's also a Java project?

Maybe aCute can be enhanced by adding a dedicated Eclipse Project Facet which can be also enabled by Eclipse-Project-Menu->Configure->Add dotnet Nature (or Add dotnet Capabilities)

What would be the benefit of this over a plain project, as long as files are properly editable, and Run/Debug is working?

[nimo23]

That is not expected. Does the project also contain some .java or pom.xml file that would make Eclipse guess it's also a Java project?

No, the project is a pure dotnet project without any java sources or pom.xml.

What would be the benefit of this over a plain project, as long as files are properly editable, and Run/Debug is working?

Okay, if it worked like that, it wouldn't really be necessary..

[mickaelistria]

No, the project is a pure dotnet project without any java sources or pom.xml.

OK. If possible, please share a minimal project that reproduces the issue with detailed steps to reproduce.

[nimo23]

You can use any simple .NET project (in my case, a simple "Hello World" project).

I think the problem is that this plugin only works on Windows and not on Mac OS (Silicon).

[nimo23]

I found the issue:

When importing an existing dotnet-project into Eclipse (by using File->Import->Projects form Folder or Archive), Eclipse automatically creates a .classpath-file and a .project-file for java projects - which is in this case wrong.

So we need to import a dotnet-project by using Import->Projects from Git->Existing Local Repository->Import as general project, then no.classpath-file and a .project-file are generated.

When using File->New->Other->NET Core->.NET Core Project, we can create a dotnet-project.

Please also provide a File->Import->Other->NET Core->.NET Core Project (which is currently missing).

[mickaelistria]

When importing an existing dotnet-project into Eclipse (by using File->Import->Projects form Folder or Archive), Eclipse automatically creates a .classpath-file and a .project-file for java projects - which is in this case wrong.

A .project file is expect, but there should be no reason to create a .classpath file.
I've tried File > Open Projects from Filesystem (same wizard) and pointing to the project located in this repository under org.eclipse.acute.tests/projects/csproj and got it imported without anything related to Java.
Please share detailed steps to reproduce from scratch (clean project, clean IDE)

[nimo23]

I've tried File > Open Projects from Filesystem (same wizard) ..

I only have File->Import->General->File System which does not work. I get the error Source is the hierarchy of destination. Nevertheless, Import->Projects from Git->Existing Local Repository->Import as general project works without issues.

In summary: I think for non-Git projects and for practical reasons, aCute could add the menu facet:

File->Import->Other->NET Core->.NET Core Project .