Many conclusions from a 4mb size changeOr it could be that there is an issue in 9.00 that is seemingly intermittent and random (as all bugs are, until understood), in which case the first course of action is to recompile with optimizations off, runtime checks on, instrumentation on, logging on, which will generally expand the exe and usually flush out (or sometimes, "fix") the issue.
You might wonder how the heck turning supposedly benign things like instrumentation and logging on could possibly "fix" an issue if they are not altering the logic of the application code in any way. The easiest-to-visualize explanation is that the instrumentation and logging takes time, and the full applicable folk wisdom here is:
Time heals all wounds, and some bugs too ;-)
Eg, if the program is measuring elapsed time between two events, then the extra slowness might be enough to eliminate cases of elapsed time (apparently) = zero, by stretching them out to be greater than the timer minimum resolution. Or to stretch out UI updates to be across frame updates, and that happens to reorder blits such that a copy from an complete image on one frame is now being made from a completed image of the following frame.
Whatever the reason for the size increase: don't panic yet (it doesn't sound like you are, but... just in case). Erel's track record is that critical issues within his domain are usually resolved immediately, and sometimes even quicker.
VB Version 1.0 came on two 1.4MB floppies. The second disk had the help flies on it. It was a brilliant innovation in its day. I went to a UK launch event for it and there was spontaneous applause when the presenter wrote and ran a UI program in about 5 minutes.I miss the days where you could fit tons of stuff on a 1.4MB Floppy.
I was looking for old stuff just I remembered I had on 3.5" floppies this week end actually and I found the original Microsoft floppies for the following Microsoft Basic versions: QuickBasic 4.5, Visual Basic for DOS v1.0 (copyright stamp from 1992) and Visual Basic for Windows 3.0. More recent versions were on CD I believe. I did write a lot of QuickBasic 4.5, some programs used to support older equipment are still used where I work. I still use VB 6.0 now even though under Windows 10 there are issues installing and running it but I have so much code to reuse it is just tempting when I need to throw something together quickly. I am trying to switch to B4J but while there are definite advantages, I am not at the level where I want to be yet.Yes that was brilliant too. I wrote some really useful stuff with that.
I'd have to disagree with this statement, as you say you have not done it! There are a lot of minor irritating issues to sort out in trying to convert a VB app to VB.NET!You may be able to migrate them to VB.NET without too much effort. I have not done it but in the typical Microsoft way, they make it relatively easy to migrate up. Some hand modifications will be required but probably not more than 10% of a full rewrite.
I currently have VB6 installed under Win10. My business software was originally written with vb6 and I still occasionally do minor upgrades etc.I still use VB 6.0 now even though under Windows 10 there are issues installing and running it