The second option is to use the same VBUC, but run a detailed analysis using the “Assessment” option. In the future we will add additional heuristics to eliminate the possibility of false positives. FYI, this was done to speed up the analysis process. You should note, however, that there may be small changes that keep the same amount of code (assignments, calls to different functions, etc), so there is no guarantee they are exactly the same. In practice, they are normally the same file copied over several projects. As shown in the screenshot below, the Assessment Tool identifies “Potential Duplicates”, which are files that have the same name and the same amount of effective (code + design) lines of code. This brand-new assessment tool considers both Shared and Duplicate files and counts both accordingly in separate columns. The first one is to download and run our new Visual Basic 6.0 and ASP Assessment Tool. If you do need to find out the number of lines of code counting these files once, we offer you two options: This may increase the final amount of lines of code of the total solution. This means that it counts shared files and duplicate files each time they appear. This number displayed in the VBUC includes all the lines of code from files referenced in the *.vbp project. If you create a migration solution using the VBUC, it counts the lines of code in a project ( Lines column): One question commonly asked by our customers is how both duplicate (same file copied in several projects) and shared files (one copy of the file referenced from multiple projects) are counted. In General // Tags: VBUC, Visual Basic Upgrade Companion //
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |