Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.
AlwaysLearning started following MonoDevelop 2.0 Alpha 1 and OSX's Mono 2.0.1 Problem
AlwaysLearning replied to Draekz's topic in Mac Programming and DevelopmentI ran into this same issue last night when trying to get project that I'd started in VisualStudio working under MonoDevelop with System.DirectoryServices project references. Even after installing libmono-system-ldap1.0-cil, and seeing it listed by gacutil, it still took me a while to figure out what the issue was - and it all makes sense now after I'd come back to it tonight. MonoDevelop filters the registered packages listed in the Edit Reference window to the .NET version of the project (as opposed to the solution). If you go to the Project's Options / Build / General and check the configured Runtime version, it will need to match the version of the libraries you want to use. In my case this was a Mono / .NET 2.0 project, which I wanted to keep as .NET 2.0, so I then had to find and install libmono-system-ldap2.0-cil. After restarting MonoDevelop, lo-and-behold it was listed in the Edit Reference window. Hope this helps!