I went through the following two examples to get an idea of how to create a custom, local Routing Task This is a walkthrough that takes you step by step through the creation of your first routing geoprocessing package: http://resources.arcgis.com/en/help/runtime-wpf/concepts/index.html#/How_to_author_and_publish_a_geoprocessing_model/0170000000m5000000/. And here is the second part, that completes the picture and shows you how to run it from code: http://resources.arcgis.com/en/help/runtime-wpf/concepts/index.html#/How_to_develop_a_point_to_point_routing_application/0170000000m6000000/ I was able to get it to run using my map package that I created (with my own vector data). However, when it runs and I click the "Solve" button, I can only get the Route graphic to display, that was displayed when I created the gpk from the result. The two points that I click on when running the code are obviously not used by the code to create the resulting Route graphic. I don’t know what I’m doing wrong with this example. Aren’t you supposed to be able to use a gpk file to (in a sense) run that same model, but with different data each time? Thanks, Renee
closed as too localized by PolyGeo, Chad Cooper, Devdatta Tengshe, iant♦ Jun 2 at 16:20
This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.
I was able to determine that the reason the code wasn't running right was because I needed to change GPFeatureRecordSetLayer("Input Locations") to GPFeatureRecordSetLayer("Input_Locations")
Such a minor thing, and I must have looked at the URL for the local runtime server a dozen times and didn't think about this because the name of the input parameters in the model had the space and not the underscore, and there was never an error or anything.