No Cosmos Operating System template in VS 2017

[V-Volte]

Area of Cosmos - What area of Cosmos are we dealing with?

Expected Behaviour

A Cosmos solution containing two projects: Cosmos Kernel and Cosmos Boot.

Actual Behaviour

Only Cosmos Kernel is created, no Cosmos boot project.

Reproduction

By Installing Devkit

Version

Devkit, Commit: ccb8fae

I had devkit on my old laptop for VS 2015 Professional and it worked perfectly. But this time, there is only one Cosmos template: Create Cosmos Kernel, and when I try to debug without altering any code, it says there were build errors.

Error: System.ArgumentException: The Path is not of legal form

I have already reinstalled Cosmos, but the issue still persists.

[fanoI]

Maybe you have accented letters in your VS project path?

[V-Volte]

@fanoI No, I don't have any accented letters. There is a space though.

I tried reinstalling VS, but it is still the same.

[Arawn-Davies]

I don't think the current project system has/uses Cosmos boot projects anymore, only the kernel project.
If you're wanting to split projects up into rings (albeit without the ring attributes), then what I did was remove the kernel overrides and inheritance from the new projects Kernel.cs, and remove the Cosmos.Build NuGet package, then referencing the new project in the old one.

Also, I don't think there can be spaces in the project path, which is another bug that ought to be fixed.

However, this did work until a couple of commits ago, when isolated assembly referencing was implemented. Not sure what happened exactly because I updated the old projects to include the 'cosmos' runtime identifier, but it's still not working :/
I'm going to open a new issue to explain exactly what's going on, bit of a bigger problem to say here.

[Arawn-Davies]

#957 is the issue, might be related, might not be so I've opened a separate one

[V-Volte]

@Arawn-Davies I created a new project in another place. The path now doesn't contain any spaces. But when I open the file, it says 'The type or namespace 'System' couldn't be found'. It does this for every single keyword in the project. I tried to add a reference, but there were none to choose.

P.S. I just found something. There is no Cosmos folder in my %appdata%. I'll try reinstalling and maybe this will solve it

Nope, it just reverted back to 'The Path is not of legal form' error after I reinstalled COSMOS, even if there are no spaces in the new path.

[zarlo]

@V-Volte in the devkit the boot project was removed

[human-being-1]

Someone, Re-Add The Boot Project.

[jp2masa]

Why do you want the Boot project? Is there any feature missing in the new project system?

[human-being-1]

The Boot Project (Obviously) Boots up The OS.

[db-noop]

No, you can just press Run

[human-being-1]

Oh. Maybe VMWare Player Missing?

[db-noop]

what do you mean?

[human-being-1]

VMWare Player might Not Be Installed.

[human-being-1]

Also, in VS2017, "Cosmos Operating System" is "C# Operating System" for C# OSs and "VB.NET Operating System" for VB.NET.

[human-being-1]

I use the User Kit.

[human-being-1]

()

[human-being-1]

()

[human-being-1]

I Think the .NET Framework 4.7.1 or .NET Core 2.0 Workload is Missing.

[db-noop]

please make a separate issue

[human-being-1]

OK

[human-being-1]

"Nope, it just reverted back to 'The Path is not of legal form' error after I reinstalled COSMOS, even if there are no spaces in the new path."

Umm, Change the Path back.

[V-Volte]

After doing everything I could, the compiler now returns only one error: Project couldn't be booted or something like that.

[human-being-1]

Try Updating Your Cosmos Devkit Version Because There has been Many Commits after commit ccb8fae.

[V-Volte]

Funny how this is, but all this happens only on my new machine but works perfectly fine on my old one.

[jp2masa]

@V-Volte If you still have this problem, please copy the output window content for the Build and Package Manager panes, and a screenshot of the error list may be useful as well.