Introducing the all-new TIBCO Community site!

For current users, please click "Sign In" to reset your password and access the enhanced features. If you're a first-time visitor, we extend a warm welcome—click "Sign Up" to become a part of the TIBCO Community!

If you're seeking alternative community sites, explore ibi, Jaspersoft, and Spotfire.

Jump to content

What is the best way to deploy 2 connectors with a reference to the same shared dll but with different versions


Manoj Chaurasia

Recommended Posts

We currently are in a state where we're building 2 separate connectors. Both connectors share a reference to a shared code base through a nuget dependency.

Connector A

|

-->Shared.dll v1.0.0.123

Connector B

|

-->Shared.dll v1.0.0.345

 

 

Our issue is that when we update the version of the shared dependency and then we build or update only one of our connectors with the new reference. When we try and load that connector in the Scribe UI We get a failed to find reference to the older Shared.dll.

Link to comment
Share on other sites

  • 5 weeks later...

Hey Jeff,

The guidance suggesting by Microsoft to get two separate versions to load is to make the version part of the name via strong naming them: https://docs.microsoft.com/en-us/dotnet/standard/library-guidance/strong...

 

One thing to note, because connectors are essentially plugins, you do not have access to the normal mechanism of binding redirects.

 

Best,

Nate

Link to comment
Share on other sites

  • 3 weeks later...
Do you know of any abnormal mechanisms for doing binding redirects then We've now added a 3rd connector which are all referencing serilog to keep our logging framework in sync. So now every time we want to update one of these project references, we basically have to build and deploy all three connectors and force our teams to deploy them all at the same time.
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 months later...

@Nate Keefe/ @Fuzz Schroederany ideas about this I'm curious of the same thing.

 

It seems that independently of even our own connectors we develop, if we make a Scribe solution that needs to run a cloud provided connector on-premise we would also run at risk of collisions depending on what those connectors reference, is that true

Link to comment
Share on other sites

×
×
  • Create New...