General
-
Add documentation - please. Add more source code comments/intellisense -- only Events.cs has XML.
Please add proper documentation, FAQ, source code comments (commenting), and source XML comments (for IntelliSense).
I think the project looks like a good idea, but takes quite a bit of looking around to figure out how everything works (looking at Unit Tests, code, etc.)
8 votesI’ve started this task by creating a sample application with four different ways of working with nvents. Please take a look at https://github.com/loraderon/nvents/tree/master/src/Samples
-
6 votes
-
Make Discovery occur in background
It looks like the Publish call for WCF publishes to each server on a background thread, but finds the servers on the main thread. This can cause delays while the servers are found. It would seem that the finding of the servers could also happen on a background thread and let the main program continue directly after the Publish call.
3 votesGreat idea and easy to implement. Will probably include some other potential changes before a release is made.
-
Fix Nevent so it won't get stuck ;-)
Hello.
I’m working with Nvents for a few months now and I was very pleased till today.I'm now experiencing a stuck when calling Publish and can't continue publishing using Nvents - it sucks again and again.
I've tried calling Stop + Start on Events.Service but it doesn't help. I can't stop the process using Nvents - I'm using a plugin for that process and replacing the plugin.
Please help.
Please see the log I'm getting when calling Publish:08/04/2012 18:41:36.886: Error on handle event thread System.TimeoutException: The open operation did not complete within the allotted timeout of 00:00:00. The…
1 vote -
Error Handling suggestion
For things like TimeOut errors and such in would be nice if the operation could be retried, maybe several times with increasing delays, but not more than x number of tries.
I am rolling out a program into production, and have run into issues where I quickly received a TimeOut error (seems like a very short timeout setting somewhere?), and the event doesn't get published - but the same event goes fine shortly thereafter.
1 vote
- Don't see your idea?