The Service Bus for the Connected Business
Versioning DLL's
The component Neuron uses for it's Pipeline code step stores the fully qualified assembly name. This causes issues sometimes for people who have set up assembly versioning in their projects.
When we ask people why they are versioning an internal dll that they never intend to run side by side the most common answer we get is so they can be sure the right one is deployed to production.
So, how can you achieve a process where you provide yourselves this kind of information and not break your pipelines and everything else that uses a fully qualified assembly names? Use File Versioning (AssemblyFileVersion attribute) instead of assembly versioning.
This will allow references to your strongly named dll to continue to work and will give you versioning information.
When we ask people why they are versioning an internal dll that they never intend to run side by side the most common answer we get is so they can be sure the right one is deployed to production.
So, how can you achieve a process where you provide yourselves this kind of information and not break your pipelines and everything else that uses a fully qualified assembly names? Use File Versioning (AssemblyFileVersion attribute) instead of assembly versioning.
This will allow references to your strongly named dll to continue to work and will give you versioning information.
Comment
About
Neuron ESB Product Support Forums and Communities
Latest Activity
Many times load balancing can change what the optimal solution is for a given deployment.
Unless careful consideration is given to what is trying to be accomplished then some erroneous conclusions can be arrived at...
For example, people take it a…
Seems like it happens everyday now. Any known issues with this? I would also get this error:
"A timeout (30000 milliseconds) was reached while waiting for a transaction response from the Neuron ESB service."
I am working with some iSeries dataqueue adapter code which calls the RaiseEnpointOffline/Online events. The code and documentation say these are now obsolete. Is there a new method to use or should they be removed?
Thanks!
What I wish to do is two-fold:
1) Capture the error on processing from a subscriber. I can do this by turning on auditing (which I have tested, works fine).
2) Submit the message for re-processing after I have corrected my code/data. This I do…
Badge
© 2010 Created by Neuron Admin on Ning. Create a Ning Network!
You need to be a member of Neuron ESB User Network to add comments!
Join Neuron ESB User Network