Unfortunately it's a two part-stacked problem that comes from modelling a physical PC closely. The first problem is you need to expand the 'capacity' of the virtual disk - which VMware can make easy through a GUI. The tougher part comes from expanding the logical filesystem partition contained on the disk of which there are many like fat32, ntfs and the myriad linux filesystems (ext2, ext3, jfs, xfs, zfs, ...). And Microsoft doesn't document ntfs at the level that allows this to be done easily which is why it the process has been reverse-engineered by third-parties. While I consider the commercial resizing tools to be stable, there is always a chance of data loss during the header resize, so there's risk and liability.
As users become more knowledgeable with virtualization, they'll plan ahead like making a virtual disk dynamically expanding with a large capacity like 127 GB, where the host file just goes to meet your needs. This way you never have to resize the logical partitions.
