-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.sln file support #95
Comments
It would be a great idea to add .sln support to aCute. |
For .csproj files, aCute is going to use a language server. It would
actually make sense to have this same language server also supporting
edition of .sln files.
It seems like those .sln files aren't based on some metalanguage such as
XML or JSON, are they? If not, are you aware of some textmate files or
other tools for those .sln we could use in aCute?
|
I thought .sln files were based on XML, but it is not a particular object serialized into XML, it is just information about the projects stored in loosely based XML format. My advice would be to install Visual Studio Community on your PC (or a friend's PC if you only have Mac / linux, lol) & create several "solutions" each containing several projects & then open the .sln file for each "solution" in NotePad++ and just follow that pattern. If you want Visual Studio to be able to open that .sln file you need to get the pattern just right b/c Visual Studio won't tolerate small discrepancies. |
Agreed. I believe omnisharp already (somehow) supports them: OmniSharp/omnisharp-roslyn#741
No, they are a completely different text-based file format. I have an example at https://github.com/omajid/LicenseCheck/blob/master/LicenseCheck.sln, but you can generate them yourself using
Here is what I could find after lots of googling: |
Oh yeah, @omajid is correct. I was thinking of the .csproj files. |
.sln
files are meta-project files meant to collect a bunch of projects that IDEs can use. Asln
file describes what projects are part of a larger set of projects.They are generated by
dotnet new
but are also available as a new project template in aCute. But aCute doesnt really seem to use/understand them to create nested/related projects.The text was updated successfully, but these errors were encountered: