Last post May 14, 2014 08:49 PM by Xequence
May 05, 2014 08:39 PM|Xequence|LINK
Anyone have any experience creating an application where you would email a user in the system based on a subset of rules? Anything that exists that handles this with claims would be cool too. Thank you in advance.
May 06, 2014 02:57 AM|HostingASPNet|LINK
This example could help -
May 06, 2014 01:25 PM|Xequence|LINK
I was hoping for something more service oriented... I would like to decouple this application entirely.
May 06, 2014 01:54 PM|PatriceSc|LINK
Some more context would help. So my understanding is that your issue is not about how to technically send a mail. Could try to narrow down it ? What is the "based on a subset of rules" part you are talking about ?
It make me think about :
- or perhaps about an alert system based on distribution lists or whatever (basically the app would generate messages send to distribution lists based on their types or whatever and mails would be send out of band on a particular schedule or something like
Keep in mind that we know nothing about your context so something like "based on a "subset" (?) of rules" is too vague.
As it seems also about decoupling I would suggest to start by how you would like the API to look like in your client (ie which features should be exposed) rather than starting by implementing actually something so that you first focus on which features should
May 06, 2014 05:43 PM|Xequence|LINK
I have been dwelling on this, http://msdn.microsoft.com/en-us/library/aa480027.aspx, which leads me into more questions.
PatriceSc, I think workflows would work well with this and I would like do that to be my 'subset of rules'.
Anyone use this? http://blog.gauffin.org/2012/10/writing-decoupled-and-scalable-applications-2/
Here is what I have going TDD on it... lol.
public void TestDateNotification()
INotificationService notificationService = new NotificationService();
INotificationEvent _event = new NotificationEvent
Name = "Homeowner signed lease",
Value = DateTimeOffset.Now
// save routine from 100 spots
// executing code ran here... how do I tie it together?
In the scheme of things, I will try to attempt tdd on this but is a journey in itself. Thanks in advance.
May 14, 2014 08:49 PM|Xequence|LINK
I ended up using IOC with static subscriber/subscription based pattern. The cool part is that Task.Factory turns this system into an entirely decoupled piece of code when run with unitOfWOrk pattern.