Manoj Chaurasia Posted October 2, 2018 Share Posted October 2, 2018 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 More sharing options...
Nate Keefe Posted November 1, 2018 Share Posted November 1, 2018 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 More sharing options...
Manoj Chaurasia Posted November 19, 2018 Author Share Posted November 19, 2018 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 More sharing options...
Manoj Chaurasia Posted December 4, 2018 Author Share Posted December 4, 2018 Is there any way perhaps to load each connector in a different AppDomain That could possibly help with our conflict issues with different version dependencies. I think that it would be up to Scribe to implement it this way though. Link to comment Share on other sites More sharing options...
Nate Keefe Posted December 4, 2018 Share Posted December 4, 2018 @Fuzz SchroederDo you have any feedback for Jeff Link to comment Share on other sites More sharing options...
Manoj Chaurasia Posted February 22, 2019 Author Share Posted February 22, 2019 @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 More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now