ConsoleFX

ConsoleFx 1.0 is currently in beta, and it's feature-set has been frozen for this release. We have started planning the feature-set for 2.0 and later versions. Here are some of the items we have in mind. If you'd like a feature to be included ... [More] , please add a feature request to the Issue Tracker and categorize it as a feature request for ConsoleFx 2.0. Version 1.0 Final new featuresVersion 2.0 featuresVersion not yet decided Version 1.0 Final Additional validators New custom validator attributes for the following: Floating-point numbersFile masksUrlsE-mail addresses Related issue tracker item: Additional validators Improve command-line error handling Update the exception messages in all exception classes provided by ConsoleFx. The developer should be able to use these messages directly for any command-line errors. Related issue tracker item: Update exception error messages Simplify common usage scenarios Provide a much simpler mechanism in common usages, such as when there is only one program mode, or a normal program mode and a help program mode. !!Version 2.0 Features Automate usage display ConsoleFx will be able to automatically generate the usage display data from the metadata in the code. The developer will not need to manually print out the usage display by writing many Console.WriteLine() statements. Usage display plug-ins Instead of fixing the way in which the usage display is generated, we will provide this as a simple plug-in mechanism, with ConsoleFx providing a default plug-in class out-of-the-box.Developers can write their own plug-ins for changing the way the application displays it's usage.Note: Depending on time, we might release additional usage display plug-ins out-of-the-box. Console window handling attribute New attribute(s) that will control the behavior of the console window, such as how to handle Ctrl+C key presses. Also allows to specify parameters to initialize the console window, such as setting it's height and width. Version not yet decided Multi-language support Multi-language support for the usage display, switch names, etc. ConsoleFx GUI front-end Windows GUI application that will accept a command-line EXE application written in ConsoleFx, and dynamically generate a Windows UI for entering the command-line arguments. Configuration file support Ability to override default command-line argument values from a configuration file. ASCII art support Support for generating ASCII art from strings and from image files. [Less]

ConsoleFx 1.0 is currently in beta, and it's feature-set has been frozen for this release. We have started planning the feature-set for 2.0 and later versions. Here are some of the items we have in mind. If you'd like a feature to be included ... [More] , please add a feature request to the Issue Tracker and categorize it as a feature request for ConsoleFx 2.0. Version 1.0 Final new featuresVersion 2.0 featuresVersion not yet decided Version 1.0 Final Additional validators New custom validator attributes for the following: Floating-point numbersFile masksUrlsE-mail addresses Related issue tracker item: Additional validators Improve command-line error handling Provide more information on command-line exceptions, and make the default error messages more user-friendly. Simplify common usage scenariosProvide a much simpler mechanism in common usages, such as when there is only one program mode, or a normal program mode and a help program mode. !!Version 2.0 Features Automate usage displayConsoleFx will be able to automatically generate the usage display data from the metadata in the code. The developer will not need to manually print out the usage display by writing many Console.WriteLine() statements. Usage display plug-insInstead of fixing the way in which the usage display is generated, we will provide this as a simple plug-in mechanism, with ConsoleFx providing a default plug-in class out-of-the-box.Developers can write their own plug-ins for changing the way the application displays it's usage.Note: Depending on time, we might release additional usage display plug-ins out-of-the-box. Console window handling attributeNew attribute(s) that will control the behavior of the console window, such as how to handle Ctrl+C key presses. Also allows to specify parameters to initialize the console window, such as setting it's height and width. Version not yet decided Multi-language supportMulti-language support for the usage display, switch names, etc. ConsoleFx GUI front-endWindows GUI application that will accept a command-line EXE application written in ConsoleFx, and dynamically generate a Windows UI for entering the command-line arguments. Configuration file supportAbility to override default command-line argument values from a configuration file. ASCII art supportSupport for generating ASCII art from strings and from image files. [Less]

ConsoleFx 1.0 is currently in beta, and it's feature-set has been frozen for this release. We have started planning the feature-set for 2.0 and later versions. Here are some of the items we have in mind. If you'd like a feature to be included ... [More] , please add a feature request to the Issue Tracker and categorize it as a feature request for ConsoleFx 2.0. Version 1.0 Final new featuresVersion 2.0 featuresVersion not yet decided Version 1.0 Final Blah Additional validatorsNew custom validator attributes for the following: Floating-point numbersFile masksUrlsE-mail addresses Related issue tracker item: Improve command-line error handlingProvide more information on command-line exceptions, and make the default error messages more user-friendly. Simplify common usage scenariosProvide a much simpler mechanism in common usages, such as when there is only one program mode, or a normal program mode and a help program mode. !!Version 2.0 Features Automate usage displayConsoleFx will be able to automatically generate the usage display data from the metadata in the code. The developer will not need to manually print out the usage display by writing many Console.WriteLine() statements. Usage display plug-insInstead of fixing the way in which the usage display is generated, we will provide this as a simple plug-in mechanism, with ConsoleFx providing a default plug-in class out-of-the-box.Developers can write their own plug-ins for changing the way the application displays it's usage.Note: Depending on time, we might release additional usage display plug-ins out-of-the-box. Console window handling attributeNew attribute(s) that will control the behavior of the console window, such as how to handle Ctrl+C key presses. Also allows to specify parameters to initialize the console window, such as setting it's height and width. Version not yet decided Multi-language supportMulti-language support for the usage display, switch names, etc. ConsoleFx GUI front-endWindows GUI application that will accept a command-line EXE application written in ConsoleFx, and dynamically generate a Windows UI for entering the command-line arguments. Configuration file supportAbility to override default command-line argument values from a configuration file. ASCII art supportSupport for generating ASCII art from strings and from image files. [Less]

ConsoleFx 1.0 is currently in beta, and it's feature-set has been frozen for this release. We have started planning the feature-set for 2.0 and later versions. Here are some of the items we have in mind. If you'd like a feature to be included ... [More] , please add a feature request to the Issue Tracker and categorize it as a feature request for ConsoleFx 2.0. Version 1.0 Final new featuresVersion not yet decided Version 1.0 Final Additional validatorsNew validators for floating numbers, e-mail addresses, web page url's, file masks, etc. Improve command-line error handlingProvide more information on command-line exceptions, and make the default error messages more user-friendly. Simplify common usage scenariosProvide a much simpler mechanism in common usages, such as when there is only one program mode, or a normal program mode and a help program mode. Version not yet decided Automate usage displayConsoleFx will be able to automatically generate the usage display data from the metadata in the code. The developer will not need to manually print out the usage display by writing many Console.WriteLine() statements. Usage display plug-insInstead of fixing the way in which the usage display is generated, we will provide this as a simple plug-in mechanism, with ConsoleFx providing a default plug-in class out-of-the-box.Developers can write their own plug-ins for changing the way the application displays it's usage.Note: Depending on time, we might release additional usage display plug-ins out-of-the-box. Multi-language supportMulti-language support for the usage display, switch names, etc. ConsoleFx GUI front-endWindows GUI application that will accept a command-line EXE application written in ConsoleFx, and dynamically generate a Windows UI for entering the command-line arguments. Configuration file supportAbility to override default command-line argument values from a configuration file. Console window handling attributeNew attribute(s) that will control the behavior of the console window, such as how to handle Ctrl+C key presses. Also allows to specify parameters to initialize the console window, such as setting it's height and width. ASCII art supportSupport for generating ASCII art from strings and from image files. [Less]

ConsoleFx 1.0 is currently in beta, and it's feature-set has been frozen for this release. We have started planning the feature-set for 2.0 and later versions. Here are some of the items we have in mind. If you'd like a feature to be included ... [More] , please add a feature request to the Issue Tracker and categorize it as a feature request for ConsoleFx 2.0. Version 1.0 Final new featuresVersion not yet decided !! Version 1.0 Final Additional validatorsNew validators for floating numbers, e-mail addresses, web page url's, file masks, etc. Improve command-line error handlingProvide more information on command-line exceptions, and make the default error messages more user-friendly. Simplify common usage scenariosProvide a much simpler mechanism in common usages, such as when there is only one program mode, or a normal program mode and a help program mode. !! Version not yet decided Automate usage displayConsoleFx will be able to automatically generate the usage display data from the metadata in the code. The developer will not need to manually print out the usage display by writing many Console.WriteLine() statements. Usage display plug-insInstead of fixing the way in which the usage display is generated, we will provide this as a simple plug-in mechanism, with ConsoleFx providing a default plug-in class out-of-the-box.Developers can write their own plug-ins for changing the way the application displays it's usage.Note: Depending on time, we might release additional usage display plug-ins out-of-the-box. Multi-language supportMulti-language support for the usage display, switch names, etc. ConsoleFx GUI front-endWindows GUI application that will accept a command-line EXE application written in ConsoleFx, and dynamically generate a Windows UI for entering the command-line arguments. Configuration file supportAbility to override default command-line argument values from a configuration file. Console window handling attributeNew attribute(s) that will control the behavior of the console window, such as how to handle Ctrl+C key presses. Also allows to specify parameters to initialize the console window, such as setting it's height and width. ASCII art supportSupport for generating ASCII art from strings and from image files. [Less]

ConsoleFx 1.0 is currently in beta, and it's feature-set has been frozen for this release. We have started planning the feature-set for 2.0 and later versions. Here are some of the items we have in mind. If you'd like a feature to be included ... [More] , please add a feature request to the Issue Tracker and categorize it as a feature request for ConsoleFx 2.0. Version 1.0 Final new featuresVersion not yet decided anchor:version1!! Version 1.0 Final Additional validatorsNew validators for floating numbers, e-mail addresses, web page url's, file masks, etc. Improve command-line error handlingProvide more information on command-line exceptions, and make the default error messages more user-friendly. Simplify common usage scenariosProvide a much simpler mechanism in common usages, such as when there is only one program mode, or a normal program mode and a help program mode. anchor:unversioned!! Version not yet decided Automate usage displayConsoleFx will be able to automatically generate the usage display data from the metadata in the code. The developer will not need to manually print out the usage display by writing many Console.WriteLine() statements. Usage display plug-insInstead of fixing the way in which the usage display is generated, we will provide this as a simple plug-in mechanism, with ConsoleFx providing a default plug-in class out-of-the-box.Developers can write their own plug-ins for changing the way the application displays it's usage.Note: Depending on time, we might release additional usage display plug-ins out-of-the-box. Multi-language supportMulti-language support for the usage display, switch names, etc. ConsoleFx GUI front-endWindows GUI application that will accept a command-line EXE application written in ConsoleFx, and dynamically generate a Windows UI for entering the command-line arguments. Configuration file supportAbility to override default command-line argument values from a configuration file. Console window handling attributeNew attribute(s) that will control the behavior of the console window, such as how to handle Ctrl+C key presses. Also allows to specify parameters to initialize the console window, such as setting it's height and width. ASCII art supportSupport for generating ASCII art from strings and from image files. [Less]

Add validators for the following:1. floating-point numbers2. file masks3. e-mail addresses4. urls

Add validators for the following:1. floating-point numbers2. file masks3. e-mail addresses4. urls

Update the ConsoleFx exception messages to be user-friendly, so they can be directly displayed when an error occurs.

Creating properties for assigning the ParameterProperty attribute is very cumbersome. It will be useful to also allow public fields to be decorated with this attribute.