btw, this is already on master: mono/mono#14660, not that i’m familiar with how mono governance is, and how it ships, just wondered how it impacts Unity to adopt this feature sooner
I can Run Project or Start Without Debugging but no debugging. I've tried right clicking the project in the inspector and clicking Set As Startup Project but this seems to be doing nothing
how MonoDevelop can benefit from this?
https://devblogs.microsoft.com/dotnet/joining-the-net-foundation-maturity-model-pilot/
https://devblogs.microsoft.com/dotnet/joining-the-net-foundation-maturity-model-pilot/
@knuxbbs The new programs of .NET Foundation are for external projects (outside of Microsoft) such as MiniProfiler, while Mono/MonoDevelop are projects under Microsoft umbrella. The issues/pains of MonoDevelop today are caused by the fact that VS for Mac takes the highest priority and 8.x series have far too many breaking changes, so MonoDevelop for Windows/Linux is significantly broken and didn't get enough attention to be fixed. To me the only solution is a change on Mono/MonoDevelop's internal project management. I don't expect much improvement before .NET 5, as VS for Mac/.NET 5 are still of higher priority.
@eon2 Unity asked you to use third party IDE https://blogs.unity3d.com/2018/01/05/discontinuing-support-for-monodevelop-unity-starting-in-unity-2018-1/ and MonoDevelop is not in the list. You should follow its official advice, as the Unity guys do work closely with those IDE vendors to ensure best user experience.
Has anyone seen a case where a particular project in a solution (using .NET standard 2.0) seems to be unable to find the System namespace? Visual Studio is happy with the entire setup, but Monodevelop seems to complain. I couldn't get a web search to show anything up about this. No other projects in the solution are affected by this oddity
It's the very first line in the CS file, but the system insists that it cannot be found. I even created a new project (.Net standard 2.0) and it makes the same complaint within the solution. It's very odd indeed. All other projects in the solution use .NET standard 2.0 and find the System namespace without issue.
Ahah... Now that's just odd. The default namespace seemed to be wrong in the project options. I just noticed when hunting around. That seems like an odd cause for the problem to me. Correcting it, the System namespace is found and things stop whining.
Just tried a STD2.0 library with same result as you are seeing - with
using System; Consoledoes not exist - funny though entering in System. gives me the intellisense completion list for the System namespace, but then selecting something in the namespace ie Console - the selected item System.Console 'does not exist' !?!
Pure chance I found it - the error messaging is complete garbage.
I also don't understand why this is a compile-breaking error for the project itself.
That seems to be all that was needed.
This is just building that single project - it's self-contained as a library for other projects in the solution to draw upon
MonoDevelop is 7.8.4 it seems; not sure whether that's important or not.
zero love
@knuxbbs "MonoDevelop could be to dotnet world what Eclipse IDE is to Java". Do you mean that all .NET guys should drop MonoDevelop, just like Java guys dropped Eclipse?
It's true that VS for Mac builds that same solution without any trouble at all. I've just noticed that MD for Linux isn't being actively packaged by anyone (from what I could see). I'll think about building from source and see if that at least gets me something usable/useful. I hadn't been aware that things had degraded so much in the MD for Linux world. Is VS Code + addons a viable replacement in any meaningful project size?
@philstopford VSCode has been a feasible alternative for years, and throughout the .NET Core years Microsoft has been trying hard to make that a better option (many .NET Core CLI verbs were added to assist), for projects big and small. However, VSCode lacks of certain features (visual designer for GTK# for instance).
for "the same directory as my .exe", use
AppDomain.CurrentDomain.BaseDirectory
After huge research, i am planning to go with JavaScript Search engine with Angular/Vue.js/Meteor/React as front-end
Choice of javascript client side storage is below
1) IndexedDB
2) JScene
3) LargeLocalStorage
4) ydn db
5) PouchDB
Links for reference
https://github.com/tantaman/LargeLocalStorage
https://gist.github.com/inexorabletash/a279f03ab5610817c0540c83857e4295
http://lintool.github.io/JScene/
https://db-engines.com/en/system/LokiJS%3BPouchDB%3BSolr
Please kindly suggest which one to go...
Basically have a cross platform system which accepts huge files and finally does a full text search...
In this way, the user just needs the browser no installation is required......
hello, Im very new on this and want to write .net and csharp apps but, I just install mono and the Test: "verify Mono is working correctly" was success. I use Atom so I try with omnisharp install, had two errors wich I fix. But when I try to make the green flame turn on nothing nothing happend, never light up. Ive being reading and omnisharp not longer suppourted, so Ive wondering, if I already have mono working fine, what editor should use?
@prog20901 You'd better post elsewhere, as your question has nothing to do with mono/monodevelop.