|Important||This document may not represent best practices for current development, links to downloads and other resources may no longer be valid. Current recommended version can be found here. ArchiveDisclaimer|
Domain-Specific Language Tools
A domain-specific language, unlike a general-purpose language, is designed to be useful for a specific task in a fixed problem domain. By using Domain-Specific Language Tools, you can build customized modeling tools. You can define a modeling language and implement it very simply. For example, you can create a specialized language that describes a user interface, a business process, a database, or the flow of information, and then you can generate code from those descriptions.
You can use Domain-Specific Language Tools to generate visual designers that are customized for your problem domain. For example, you can create a tool to describe concepts that are specific to how your organization models business processes. If you are building a state chart tool, you can describe what a state is, what properties a state has, what kinds of states exist, how transitions between states are defined, and so on. A state chart that describes the status of contracts in an insurance company is superficially similar to a state chart that describes user interaction among pages on a Web site. However, their underlying concepts differ significantly. By creating your own domain-specific language and custom generated designer, you can specify exactly what state chart concepts you need in your tool.
For the most recent information about Domain-Specific Language Tools, see Domain-Specific Language Tools on MSDN (http://go.microsoft.com/fwlink/?LinkId=59984).
In This Section
Provides conceptual, walkthrough, and how-to topics about creating designers for domain-specific languages by using Domain-Specific Language Tools.
Covers managed reference.