At which point I realized that Visual Studio was running a cached version of my application.
Now when this used to happen in IIS on the server, we used to bounce IIS to clear its cache.
So I changed the Contract file to add those two functions. Puzzled I uncommented a "debugger" line in the function call the "missing' function.
The debugger never was hit and when the Contract dynamic file open to show the error, the "debugger" line was still commented out.
Now script is being changed and being run, but still the cached page is being displayed. In addition, I am noting that when you step through scripts and code, instead of being returned to the browser's display of the web site, it is now necessary to manually minimize the VS2012 interface. That way I can be sure user get the latest updates.but again I see that it still isn't 100% effective.— A threshold that enforces a pre-filter roundtrip to prefilter search shards based on query rewriting if the number of shards the search request expands to exceeds the threshold.On a side note, the ability for apps to update themselves without the App Store has been around for a quite a while, though only for apps created using Java Script frameworks such as facebook’s React Native and services such as apphub.Rollout is simply the first and only solution that provides the ability to push code-level updates to native Objective-C and Swift apps.It is meant to tweak or fix them, avoiding the minor releases needed to fix bugs, add logging or tracking, update messages, force users to upgrade, etc.For new features or functionality you need to release through the app store.The second condition, no new features or functionality, is really up to you.Rollout isn’t intended to push new features or functionality.This filter roundtrip can limit the number of shards significantly if for instance a shard can not match any documents based on it’s rewrite method ie.if date filters are mandatory to match but the shard bounds and the query are disjoint.