Namespace and nuget errors in empty project
See original GitHub issueArea of Cosmos - What area of Cosmos are we dealing with?
Opening new project
Expected Behaviour - What do you think that should happen?
the examplecode opens without errors
Actual Behaviour - What unexpectedly happens?
In the examplecode that shows up after the project-creation-process,
using Sys = Cosmos.System
, BeforeRun()
, Run()
is marked as an Error.
There are allso 8 Errors in the Errorlist:
- CS0246 The type or namespace name ‘Cosmos’ could not be found (are you missing a using directive or an assembly reference?)
- CS0115 ‘Kernel.BeforeRun()’: no suitable method found to override
- CS0115 ‘Kernel.Run()’: no suitable method found to override
- NU1101 Unable to find package Cosmos.Build. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, nuget.org
- NU1101 Unable to find package Cosmos.System2. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, nuget.org
- NU1101 Unable to find package Cosmos.Debug.Kernel. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages, nuget.org
- NETSDK1056: Project is targeting runtime ‘cosmos’ but did not resolve any runtime-specific packages. This runtime may not be supported by the target framework.
- Project is targeting runtime ‘cosmos’ but did not resolve any runtime-specific packages for the ‘Microsoft.NETCore.App’ package. This runtime may not be supported by .NET Core.
Reproduction - How did you get this error to appear?
I installed the cosmos “User Kit” as explaned on the cosmoswebsite https://www.gocosmos.org/docs/install/ Then I started creating my project like this github site explains https://github.com/CosmosOS/Cosmos/wiki/Develop-Your-Own-Operating-System-in-C%23-or-VB.NET
When the project was displayed, there were these errors.
Version - Were you using the User Kit or Dev Kit? And what User Kit version or Dev Kit commit (Cosmos, IL2CPU, X#)?
I was using the CosmosUserKit-20190628-vs2019.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7
Top Results From Across the Web
NuGet error on site build & custom namespaces not seen ...
On the following screen selected Empty application then clicked OK. Right clicked the project in Solution Explorer, clicked NuGet console, ...
Read more >Namespace error with nuget package - Microsoft Q&A
The nuGet add seems to work fine, and the package shows up in the dependencies for the project in the solution explorer and...
Read more >namespace System didn´t find it · Issue #182
In my case, this problem is solved by update NuGet packages. The type of my project is SAP. First, right click the UWP...
Read more >PackageReference in project files - NuGet
Package references, using <PackageReference> MSBuild items, specify NuGet package dependencies directly within project files, as opposed to ...
Read more >NuGet Restore task fails for .Net Core project migrated with ...
Dear all, I have .Net Core project which has been converted with Visual Studio 2017. The build plan especially the task NuGet Restore...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, visual studio community 2019 is supported. Although gocosmos.com’s tutorial is outdated, the perquisites it lists for the userkit are still required for visual studio 2019. The most recent release to the userkit is the first to support only vs 2019, before that, they supported only vs 2017.
Hello; I’m bumping this issue since I have produced the same errors as the op’s first post from creating a new Cosmos project.
Out of curiosity, what prerequisites are needed for Cosmos to run on VS 2019 Community (if it is supported)? The installation guide on gocosmos.com seems to be outdated and only outlines installation for VS 2017.