Isn't there a way to embed some environmental data in a sink registration item so the sink can tell when it's running in a dev or prod environment, for example? I've been digging through Rizzo and Martin, and I can't find this mentioned, though I'm sure there was someplace where we could do this...
Yes. Check out the training sample from Chapter 15. I use the event sink registration item to store custom properties. You could do the same thing but make those properties say whether it's running in a dev or test environment. Tom -- Looking for a good book on programming Exchange, Outlook, ADSI and SharePoint? Check out http://www.microsoft.com/MSPress/books/5517.asp "Rick" wrote in message news:1124894722.631845.308750@g47g2000cwa.googlegroups.com... > Isn't there a way to embed some environmental data in a sink > registration item so the sink can tell when it's running in a dev or > prod environment, for example? > > I've been digging through Rizzo and Martin, and I can't find this > mentioned, though I'm sure there was someplace where we could do this... >
I'm not seeing this. Can you tell me where to find it? I have 3rd Ed.
However, don't store to many properties. A normal Exchange system can only have 65535 properties (if I remember correctly) totally, globally. (I once tried to store 50-1000 properties per user in the registration item. It worked fine for the customer for the first two weeks, then everything stopped.) Good luck Leif Tom Rizzo [MSFT] wrote: > Yes. Check out the training sample from Chapter 15. I use the event sink > registration item to store custom properties. You could do the same thing > but make those properties say whether it's running in a dev or test > environment. > > Tom