Sorry to keep asking stupid questions about application configurations, but I just can seem to wrap my head around how they work.
I have a custom configuration that is set to use a custom map. My expectation is that when I launch Explorer (1500) using that configuration, that my custom map will be what is displayed, but it isn't. In fact, all of the configuration's settings are completely ignored, I'm just getting the default ESRI application setup. In order to get the actual config that I want, I then have to go to the main menu --> 'Set Application Configuration' and set the radio button to 'Use application configuration located at:'. This seems like an odd requirement considering I just launched the application from this file.
Anyway, after that step, The proper app config does open and I do have all the proper custom settings EXCEPT that my custom map is still not being used. I'm still seeing the ESRI default map instead. In order to get that working, in the Application Configuration Manager, I have to make sure that the check box for 'Always open this map' is checked 'true'.
So at this point, everything is technically working, but as I understand it, anyone I share this config with will never be able to directly open any other map other than the one I created because their application will always be locked into my custom configuration (they probably won't know how to change that) AND because that configuration is set to always use my custom map. This is not what I want. I want users to be able to start with the custom map, make their own modifications, save it, and be able to get back to it later. But because of the application setup, they can never open their own saved map. No matter how they launch it, Explorer will always use my app config which is set to always open my version of the map!
I'm sure I'm missing something obvious that would solve all my problems, and if someone could point out what that obvious thing is I would be very grateful because I just can't find it. Or maybe my application is not functioning quite right. Is the application configuration behavior I described above the expected behavior???
