|
1 | 1 | # CodeFactory Ecosystem |
2 | | -CodeFactory is a collection of automation tools that are designed to be used in a native IDE(Integrated-Development-Environment). |
3 | | -The decision to integrate into the IDE is based on the fact that CodeFactory is a design time tool - meaning that no extra code artifacts or runtimes are required to be added to your final solution codebase. |
| 2 | +CodeFactory is a collection of automation tools which are designed to be used in a native IDE(Integrated-Development-Environment). |
| 3 | +The decision to integrate into the IDE is based on the fact that CodeFactory is a design-time tool - meaning that no extraneous code artifacts, libraries or runtimes are required to be included with your final solution codebase. |
4 | 4 |
|
5 | | -Throughout the life of CodeFctory more then one IDE will be supported in future releases. Which is why CodeFactory is always named after the platform it is hosted on. |
| 5 | +In the future, CodeFactory will support more than one IDE, which is why CodeFactory products are named after the platform it's hosted on (i.e. CodeFactory for Visual Studio). |
6 | 6 |
|
7 | 7 | In this section we will focus on how CodeFactory integrates into the IDE. |
8 | 8 |
|
9 | 9 | ## CodeFactory for Visual Studio |
10 | 10 | CodeFactory for Visual Studio is an extension of the Visual Studio IDE. |
11 | | -CodeFactory was designed to run as an internal service inside Visual Studio just like Razor, C#, or any number of other services that are part of Visual Studio. |
12 | | -This means that once installed CodeFactory is always 'on' and will automatically load automation commands for use when a solution is loaded. |
| 11 | +CodeFactory was designed to run as an internal service inside Visual Studio, just like Razor, C#, or any number of other services that are part of Visual Studio. |
| 12 | +This means that once installed, CodeFactory is always 'on' and will automatically load automation commands for use whenever a solution is loaded. |
13 | 13 |
|
14 | | -## CFX - Code Factory Extension |
15 | | -A CodeFactory automation project is saved as complete package in a single file called a CodeFactory extension (*.cfx). |
16 | | -This uses a similar approach as word with DOCX or Excel with XSLX files. |
17 | | -All it takes is to copy a CodeFactory extension, or CFX, file into the root of the your solutions folder. |
| 14 | +## CFX - CodeFactory Extension |
| 15 | +A CodeFactory automation project is saved as complete package within a single file called a CodeFactory Extension (*.cfx). |
| 16 | +This uses a similar approach as Word uses with DOCX or Excel with XSLX files. |
| 17 | +All it takes is to copy a CodeFactory Extension, or CFX, file into the root of the your solutions folder. |
18 | 18 | Once the solution is opened in Visual Studio it will automatically load the automation and make it avaiable for use. |
19 | 19 |
|
20 | 20 | ## CodeFactory SDK |
21 | 21 | All automation for CodeFactory was designed and delivered using the CodeFactory SDK. |
22 | | -The SDK was designed to provide straight forward access to automation and authoring of custom automation. |
23 | | -The SDK uses targeted .net framework projects that hosts all the supporting libraries that make up the CodeFactory capabilities. |
24 | | -The SDK is responsible for packaging the automation and making the final CFX Files that are used with solutions. |
| 22 | +The SDK was designed to provide straightforward access to existing automation and authoring of custom automation. |
| 23 | +The SDK uses targeted .NET Framework projects that hosts all the supporting libraries that make up the CodeFactory capabilities. |
| 24 | +The SDK is responsible for packaging the automation and generating the final CFX Files which are used with solutions. |
25 | 25 |
|
26 | 26 | [Link Here] - Back to Overview |
0 commit comments