We use VB6 and VB.NET - and both are on the AWS instance / virtual machine. 

This is a copy of Treasury Software's environment, so you can enter at any time.

At the center of the desktop are the following icons:

BRCOM.exe
Main executable, launches the software

Packaging.exe

Enables you to quickly reset (as if you re-installed the software). 
It simply deletes the program's working directory(ies):

C:\Users\Public\Treasury Software - this is the initial working directory and is always created
C:\Users\Administrator\Documents\Treasury Software - this is created only if QuickBooks Online is selected. Once this folder is created, it is the 'active' folder.

VB6 - see notes below
VB.NET - see notes below

VB6

The code is stored locally at C:\aaavb\1000
When building/compiling it creates the main executable located at C:\aaavb\1000\BRCOM.EXE
The code contains the importing wizard, ACH/EFT file creation and our legacy code that was not migrated to VB.NET.

VB.NET

The code is located at C:\aaavbDLL\1003

When building/compiling it creates the dll (and related files) and saves it into the same directory as VB6 (C:\aaavb\1000). The files are:
C:\aaavb\1000\TS_REPORTING.dll
C:\aaavb\1000\TS_REPORTING.tlb
C:\aaavb\1000\TS_REPORTING.pdb
C:\aaavb\1000\TS_REPORTING.xml

VB.NET contains the code for QuickBooks Online, Reporting, code that we've already migrated from VB6 - and most of the user interface. 

Limitations:

VB6

1. When running the software from the executable (BRCOM.exe), you have full functionality when importing Excel and csv files.
However, if you are running the software in VB6 debug mode, you cannot import an Excel file.  The workaround is to either save the Excel file as a csv file - and then import the csv file, or you'll need to open the Excel file and 'copy and paste' within the import wizard.

VB.NET

(none)

For now, please leave the instance / virtual machine running (do not shutdown).