I’m running service bus 1.1 on premise locally and have it hooked into a wcf service using netMessagingBinding. I installed Application Initialization and set Start Mode to AlwaysRunning for the application pool, and set Preload Enabled to true for the site. I also have the appropriate <applicationInitialization> section in the web config where I added the service to an initializationPage.
The message gets delivered if I hit the endpoint in my browser, and even if I do an IIS reset, it still gets delivered, however I had to hit the endpoint first manually. If I do a clean (or edit any of the wcf code files) and build, it won’t get delivered until I hit the endpoint. I get similar behavior when I set a break point in the service and attach to the w3wp.exe process. If I do a clean and build and set a break point in the service code, it has the open red circle that says breakpoint will not be hit, no symbols have been loaded for this document. When I hit the endpoint, the open red circle gets filled, and the endpoint can be hit. I’m guessing these 2 go hand in hand with what I’m seeing with the service bus.
Setting up Application Initialization fixes the issue if I restart IIS, it can continue to receive messages, however I first need to hit the endpoint. I just don’t know how it handles the scenario when it first gets deployed (like when I do a clean and build). I thought the Application Initialization would of handled this but I’m probably missing something.