Skip to main content
  • 772 Accesses

Abstract

With many applications, you can configure them to be “one size fits all,” but there will be times when you need to tell an application something unique about the environment it is running on. You have many options; here are some that come to mind:

  • Code a unique version of the application for each environment permutation (okay, probably not the best idea).

  • Pass arguments to the application when you start it from a command line or batch file.

  • Have the program query the user for the information on startup.

  • Use the Registry (yes, this solution is still available; in fact, it is still used quite frequently, but it is sort of frowned upon when developing new .NET applications).

  • Use a configuration file.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

eBook
USD 16.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

Rights and permissions

Reprints and permissions

Copyright information

© 2009 Stephen R. G. Fraser

About this chapter

Cite this chapter

(2009). .NET Configuration File Programming. In: Pro Visual C++/CLI and the .NET 3.5 Platform. Apress. https://doi.org/10.1007/978-1-4302-1054-2_9

Download citation

Publish with us

Policies and ethics