...
See also this article on the Global Stubs concepts and how this report fits in.
Target Code Scan
Anchor | ||||
---|---|---|---|---|
|
The results of searching the generated units for user-defined lists of regex patterns. The list of patterns to search for is in CodeScanList.txt file. See Search Panel
...
Optionally, you may add Folders to your solution by adding [Folder] records as illustrated below. Only one level of nesting is supported.
Sample GenerateSolution.txt file with Folders | |||
---|---|---|---|
|
You may also add additional levels of subfolders using backslash in the folder names for example:
Sample GenerateSolution.txt file with Nested Folders | |||
---|---|---|---|
|
You may edit this file to add or remove projects that will be in the solution.
If this file is not present, the solution will integrate gmStudio will create one listing all of the .NET projects in your deploy folder.
...
This Visual Studio Solution generation feature also be initiated in two other ways:
...
2) by clicking the [Generate and Open VS Solution] item from Tools menu.
Info |
---|
If you want to engage a custom Solution file Generator that can read and process GenerateSolution.txt files, you may do so by specifying the command line to run it in the gmStudio.cfg file. For example:
|
Pre-Processed Source
This report generates a bundle file (see Deployment) containing a content for a version of the VB6 source that has had some early stage pre-processing (e.g. Compile/Fix) applied by the tool. This may be useful if you have a conditional VB6 code (i.e using a lot of #if/#else) and you wish to simplify the analysis and upgrade project by working with a particular non-conditional variant of that code.
You may use the deployment tool to publish the pre-processed source files into a SrcPrep folder next to the source root folder, for example:
Code Block |
---|
"\Program Files (x86)\GreatMigrations\gmStudio\support\tools\Deploy.exe" WPFCalculator-PrepSource.bnd deploy verbose replace
|
Generate Project Signature
A project signature is information that identifies the unique set of files in your project and the total, non-blank lines of code in those files. These files are used for . This report generates a file containing a Project Signature for the selected migration tasks. A project-signature file may be used for perpetual, project-specific licensing. Contact us for more information on Project-specific licensing if our standard time-limited licensing does not meet your needs.