"Project Background"In an efficient cloud platform project, one of the benefits of creating a distributed service (i.e. WCF) for each of our modules is that we do not have to be in a solution that facilitates the invocation of interfaces between each other, as long as the reference service, the interface in the service, and the methods in the interface can be used.
"Problem description"
I have permission to register the module to invoke the interface method of the user module, under normal circumstances, I invoke the user module to publish a good service. Available if the user module
B
after I call the method change in the layer, I call it again, if it is calling it local code (in my local Build User module service), then there is no problem, but when he submits to the
SVN
, and
Jenkins
after the build was successful, I had a problem calling the published User module service: why.
"Thinking Process"
1 • User Module change the B-tier method and change the contract method of the WCF layer, which is the same solution when I tune it. 2 • After the user module has changed the method, is the NuGet released again or. 3 · I refer to the latest generation of user module Contract.dll, for cooperative development, so appropriate. 4 · or the user module changes directly, I directly invoke the published service can be.
"Temporary Positive solution" (considering that the process may be lacking,)Under normal circumstances, he can update directly, because I call him to publish a good DLL path in the corresponding physical path of his server site, this physical path is the latest DLL only, so I call the latest DLL, no other operation. Possible causes of error: 1 • The physical path to the publishing site has a problem: the physical path should be the path to the corresponding project publish file. 2 · If there is no problem with the physical path, consider whether the bin file under the physical path is not up to date. The source is the bin path in the source code of WCF, which is set in the server-side bat file. 3 · If there are no problems with the various configurations in the bat, it depends on whether the bin in the source file is up to date. The bin of this source file is built with Jenkins to copy the SVN source code to the server's workspace. So the next step is to see if the configuration process of Jenkins is missing. As shown in the figure:
It's here for the time being. Blog is a little short, the reason why I want to put myself many times to meet this problem, to solve the problem of the whole thinking process leaks out, if you read this blog, we have a sympathetic, I particularly hope to share this problem with you. The way we think about problems and how we think more effectively.
