Closed dsdude123 closed 7 years ago
The project wasn't restored for some reason. Try restoring it manually.
Can't do that on a new solution because I can't even save the project. Package manager console says "Solution is not opened or not saved. Please ensure you have an open and saved solution." and it just stops there, can't run any commands.
I tried running the restore on an older solution that I had saved and it ran successfully but the errors still remain.
Try reinstalling the User Kit.
Still doesn't work, one thing I noticed however is that my older solution has none of the errors with the System namespace. Only has errors with the Cosmos namespace.
UPDATE: If a manually reference the Cosmos DLLs, I can get my older solution to build successfully. Still no dice on making a new solution yet.
Found a workaround for this issue, it turns out that "Save new projects when created" located in Options>Projects and Solutions>General was disabled and as a result the Cosmos project was being created as a temporary project and the restore failed as a result. Enabling this option fixes the issue.
Alternatively, adding <PromptForSaveOnCreation>true</PromptForSaveOnCreation>
to the Visual Studio Templates for Cosmos should also fix the issue according to the MSDN although I have not tested this.
Thanks for the tip! I added it to the project templates in the commit so if you either built the devkit or installed those templates it will sort it out for you :)
This issue hasn't been yet resolved for me. I've talked to almost about every contributor and nothing in their power resolved it.
I couldn't save my project, as this weird error appears. It doesn't even show the project files in cache.
System, and Cosmos assembly could not be found. Restoring resulting into nothing. I've uninstalled/installed vs, user kit & dev kit.
This issue is weird. Idk why Cosmos went to 2017 that fast. Please support back 2015. .Net core sucks cause it doesn't work for me.
Not only as of me, 70% of others are having constant issues.
The same for me. But on the contrary - I'm getting errors with the System and cosmos namespaces.
We're depending on issues being fixed for a couple of other things not in our control, e.g. .NET Core 2.0 hasn't included the latest stable of Microsoft.Data.SQLite, which has fixes for the missing e_sqlite3.dll issue. These issues are also unrelated, as @dsdude123 said his issue was with the Cosmos project not saving, which was fixed by setting newly made projects to save automatically in the latest devkit (https://github.com/CosmosOS/Cosmos/commit/3dbb8678c49e14934ec9525d53b716ca4231534a at the time of this post)
These issues are unrelated, please open a new one exactly detailing what errors you are having. Also, the latest devkit is having issues regarding SQLite whereas the Userkit (20170928) isn't due to being built on .NET Core 1, so use that for the time being whilst we try and fix this.
I assume that "System and cosmos namespaces" means that the packages weren't restored, so it's still the package restore issue.
@Arawn-Davies I'm sorry, but this issue combines. He's not here just because he couldn't "Save". He came because of missing references/namespaces (System/Cosmos), and my issue and the one comment issued above is related.
Using the fix, as of updating the template to manually save does not work/save at all. The same exact thing occurs.
@jp2masa No, ? Maybe. We've discussed this in chat. I did everything on earth that was possible. Upcoming 2nd week of bringing Cosmos to life.
@LegitSoulja My issue of missing assemblies was being caused by the save issue because NuGet cannot perform a restore unless the project was saved. This is now fixed in the devkit (https://github.com/CosmosOS/Cosmos/commit/3dbb8678c49e14934ec9525d53b716ca4231534a), please open a new issue as for it is unrelated to this one. Either that or you have applied the fix for userkit incorrectly. Issue closed.
I am unable to build or even save a new solution on the newest userkit. I had to reinstall everything (VS 2017, Windows, etc.) on my computer a few days back due to an unrelated issue and I haven't been able to get Cosmos working since. I have applied the fix to Cosmos.targets from #744.
When building a new solution I get the following output:
Additionally, upon trying to save the new solution, Visual Studio displays an error that reads: "The operation could not be completed. No such interface supported."