Mappoint control usage best practices RRS feed

  • Question

  • I want to use the Mappoint control in my application.

    If I make a reference / add it to my toolbox it is useable and such.

    From the point of view of a .NET application development best practice I was wondering how I should do this to make the code as reliable and resilient as possible.

    First, I drop the control on the form.

    I use the control and all is well on my dev machine.

    When I deploy if Mappoint and the control are NOT installed how will my application react? What / how do I trap this error?

    Will the control ( can it ) be put into my assembly for redistribution?

    Can I make my installer check for the existence of Mappoint on setup?

    Should I check for the availibility in my app and create the control in code rather than dropping it on the form in the IDE?

    ANY and all guidance would be appreciated as I am coming from Delphi and would like to know how MS expects or desires us to do things within the .NEt environment.

    Monday, December 19, 2005 5:33 PM