Can you count the letter o in:
Q: Are the enterprise WSDL endpoints for Sandbox & Production the same (now)? We have built a .NET app that uses our Enterprise WSDL to pull data from Salesforce , and we use a dedicated development sandbox for ongoing development.
Previously, looking at the WSDLs generated from the two orgs, in addition to the SOAP endpoints starting w/ login.salesforce.com vs. test.salesforce.com, the Id at the end, following the API version number, also used to be different between the two.  I dont know what that Id refers to - its not the Org Id, or I wouldnt be asking the question ... probably.
I just refreshed that dev sandbox and generated new WSDLs (Production/refreshed sandbox) and the endpoints are identical.  Aside from the test vs. login, does that last ID being the same matter anymore?  (That dev team doesnt like to just try stuff out w/o evidence -- engineers...)
Thanks!

A: The ID at the end of the Enterprise WSDL URL is the VersionSet ID.

https://login.salesforce.com/services/Soap/c/39.0/0DF1000000000001

It encodes the managed package version selections when the enterprise WSDL was generated.
For example, the enterprise WSDL might include components that came from managed packages. Salesforce needs to know which version of the managed package that definition came from to keep everything consistent.
Its likely that they used do differ before the refresh as the Enterprise WSDL was retrieved from both the Sandbox and Production independently and an VersionSet was created for each. Now that the sandbox has been refreshed from production it has access to the same VersionSet. 
You can probably confirm this by looking at the pod identifier in the 4th and 5th characters of the ID.
See also:


*

*Package Version Settings

user
There are 106 "o"s in the text you provided.
assistant