To view parent comment, click here.
To read all comments associated with this story, please click here.
Mono is just an implementation of .NET created by <Microsoft> which is developed on <Windows>. And therefore it is quite sensible that Microsoft implemented classes to access registry to make .NET to cooperate with its native applications. So to make Mono compatible with .NET as much as possible, they better implement anything that Microsoft implemented. There is no big deal. I don't really get what is the problem with you. So do you want a crippled implementation which wouldn't work near 100% because you don't like some part of it? Then why not just fork Mono, remove unwanted stuff from it and use it in your own sake? Not everyone thinks the same way as you do. Please..
Now you are claiming Mono is near 100%? Have you actually even tried to use Mono for development or are you just delusional? Mono has always been implementing an incomplete .Net framework since v1.0.
The following .Net technologies are unsupported and are unlikely to be completed in Mono:
* Windows Presentation Foundation (.NET 3.0).
* Windows Workflow Foundation (.NET 3.0).
* Code Access Security (.NET 1.0).
* System.Management (All Versions)
Read about it here:
http://mono-project.com/Roadmap
-Ad





Member since:
2005-07-07
Those APIs are part of the .Net framework. The contents of those links are real, they are not FUD!
-Ad