Sample of how to below. Queue creation should be happening automatically, is it not? If not, which container are you using? I'm still not quite too clear on the reasoning behind the need. Are you saying you have two apps running concurrently with the same queue?
The reason the starbucks sample does that through hard coded strings is because it's trying to demonstrate 4 separate processes using the RemoteAppDomainHost. It's not something you typically need to interact with though unless you're writing your own host for consumers. https://github.com/hibernating-rhinos/rhino-esb/blob/master/Rhino.ServiceBus.Tests/QueueCreationModuleTests.cs#L61 var configuration = new RhinoServiceBusConfiguration() .UseCastleWindsor(container); configuration.Configure(); Purge(configuration.Endpoint); Potential API change... var configuration = new RhinoServiceBusConfiguration() .PurgeOnStart() .UseCastleWindsor(container); configuration.Configure(); On Thu, Sep 22, 2011 at 3:44 PM, Michael Lyons <[email protected]> wrote: > How about queue creation for the first run? I have no problem with the > API doing it. > > The only way I have seen queue creation and purging done in rsb is in > the Starbucks example which uses hardcoded strings (which doesn't work > with web.configuration transformations). How would you do this then > through the API. > > The reason why it is so important to the app in my situation is that > there will be multiple instances of the app running. At the moment > there is one set of queues for the customers site and then another for > a sandbox site on the same server. > > > On Sep 23, 7:13 am, Corey Kaylor <[email protected]> wrote: > > To me it makes more sense to handle the purging of queues from the API > > rather than exposing the guts of configuration in multiple places. There > are > > already ways to get the configuration information when you're not using > the > > host. Thoughts? > > > > > > > > On Wed, Sep 21, 2011 at 3:54 PM, Michael Lyons <[email protected]> > wrote: > > > It's not just RemoteAppDomainHost but other host types as well. > > > > > Essentially you are correct. It's to create or purge the queues and > > > eliminate any typo's and reduce misconfiguration from doubled up/hand > coded > > > values. > > > > > On Thursday, September 22, 2011, Corey Kaylor <[email protected]> > wrote: > > > > I guess I should more specifically, what you're trying to accomplish? > Is > > > it to purge the queues on startup? > > > > > > On Wed, Sep 21, 2011 at 6:32 AM, Corey Kaylor <[email protected]> > wrote: > > > > > >> If you're using RemoteAppDomainHost, would calling the > InitialDeployment > > > method suffice? > > > > > >> On Wed, Sep 21, 2011 at 4:36 AM, Michael Lyons < > [email protected]> > > > wrote: > > > > > >>> Is there anyway to get the RSB endpoints set in the configuration > file > > > >>> before the service bus has started? > > > > > >>> This is so that I can use the endpoint values to create my queues > like > > > >>> in the starbucks examples, but without doubling up on the values > (eg. > > > >>> In code and in a config file or in app settings and rhino service > bus > > > >>> settings). > > > > > >>> Example: > > > > > >>> var baristaLoadBalancer = new > > > >>> RemoteAppDomainHost(typeof(CastleBootStrapper).Assembly, > > > >>> "BaristaLoadBalancer.config"); > > > > > >>> PrepareQueues.Prepare(baristaLoadBalancer.Configuration.Endpoint, > > > >>> QueueType.LoadBalancer); > > > > > > PrepareQueues.Prepare(baristaLoadBalancer.Configuration.AcceptingWorkEndpoi > nt, > > > >>> QueueType.LoadBalancer); > > > > > >>> baristaLoadBalancer.Start(); > > > >>> Console.WriteLine("Barista load balancer has started"); > > > > > >>> var barista = new > > > > > > RemoteAppDomainHost(typeof(BaristaBootStrapper)).Configuration("Barista.con > fig"); > > > > > >>> PrepareQueues.Prepare(barista.Configuration.Endpoint, > > > >>> QueueType.Standard); > > > > > >>> barista.Start(); > > > >>> Console.WriteLine("Barista has started"); > > > > > >>> -- > > > >>> 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] < > > > rhino-tools-dev%[email protected]>. > > > > > >>> For more options, visit this group at > > >http://groups.google.com/group/rhino-tools-dev?hl=en. > > > > > >> -- > > > >> 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] < > > > rhino-tools-dev%[email protected]>. > > > > > >> For more options, visit this group at > > >http://groups.google.com/group/rhino-tools-dev?hl=en. > > > > > > -- > > > > 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] < > > > rhino-tools-dev%[email protected]>. > > > > > > For more options, visit this group at > > >http://groups.google.com/group/rhino-tools-dev?hl=en. > > > > > -- > > > 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. > > -- > 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. > > -- 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.
