Reading Ayende's latest blog post http://ayende.com/Blog/archive/2009/11/03/development-only-code.aspx I read it with a somewhat guilty conscience because in the service broker queue implementation I have violated this. However, in my case there is a legitimate use case for "resetting the database" in production code. The specific use case is when our windows application deployed through click once. With rhino queues this was easy and less of a concern. I'm interested in hearing others approaches for how they might achieve my goal of the following.
1. Messages sitting in queue on startup for the windows application are unimportant and should be purged. 2. Schema changes i.e. version conflicts with the current schema must be recreated without any interaction of the user or extra complexity of deployment that would fall outside of click once. I'm leaning towards conditional compilation so that I deploy a specific build for our click once application, but looking for better suggestions. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en -~----------~----~----~----~------~----~------~--~---
