Sharp.Xmpp is looking for a maintainer! Unfortunatelly I do not have currently the time needed to maintain the library. Luckily a small but vibrant community has evolved around Sharp.Xmpp. If you would like to be the project's maintainer please sent an email to pgstath@gmail.com. This should include issues, tickets and commits that you have done for Sharp.Xmpp or other similar project. Sharp.Xmpp is a multiplatform, Windows and Android, .NET XMPP client assembly.Sharp.Xmpp supports IM functionality & a variety of XMPP extensions, is simple and is extensively tested against Android Xamarin. It is a fork of the currently frozen excellent S22.Xmpp project. Sharp.Xmpp will be at the FOSSDEM 2016 Real time DevRoom!
Other
84
stars
51
forks
source link
Use default paths for assembly references added by nuget packages #44
This caused me some confusion, as it's still a relative path, albeit one that is unlikely to be valid on any given developer's machine.
I am unaware of any reason that would preclude the use of the default path, which doesn't make unnecessary assumptions about the directory structure beyond the solution level.
Of course, if I've overlooked something, feel free to let me know.
The
csprojis current configured to look in the following directories for two assembly references:This caused me some confusion, as it's still a relative path, albeit one that is unlikely to be valid on any given developer's machine.
I am unaware of any reason that would preclude the use of the default path, which doesn't make unnecessary assumptions about the directory structure beyond the solution level.
Of course, if I've overlooked something, feel free to let me know.