Trapping IDE Events

 < Free Open Study > 


"Modern science is so enamored with its ability to create that it takes no time to consider whether it is right to create".

--Les Smith

Gone are the days when you could think of an application as a series of procedures that would execute in sequence. Since the advent of Windows programming, applications programming has become event driven. This means that the developer cannot tightly control the execution flow of an application. In Windows programming, the sooner that a developer learns that the user will determine how an application will flow (if you use the word "flow" loosely), the better off he or she will be. In Windows programming, the developer must program the application to respond to anything and everything the user can do. This is one of the things that makes Windows programming so interesting. The developer must learn to anticipate, think ahead, and plan for any type of user action.

This type of programming is called event-driven programming. An event is notification to an application that something important has occurred. When the developer using Visual Studio .NET does anything—almost literally anything, such as clicking a mouse, entering a keystroke, and so on—an event is likely to occur. This is especially true if focus changes from one window in the integrated development environment (IDE) to another. It also happens when the developer presses the Enter key in a Text Editor window.

In this chapter, I show you how to trap in an add-in the IDE events as they occur.

 < Free Open Study > 

Writing Add-Ins for Visual Studio  .NET
Writing Add-Ins for Visual Studio .NET
ISBN: 1590590260
EAN: 2147483647
Year: 2002
Pages: 172
Authors: Les Smith © 2008-2017.
If you may any questions please contact us: