One thing you can do is have a global array of error messages Lets say a Custom LogItem class. Then in your base code you handle the exceptions and if catched, add item to the log array.
In App.UnhandledException you write the log array items to a file and return true.
If error IsA OutOfMemoryException Then
Return True
End If
Will likely never be called. Once youve reached an out of memory situation, just about the only thing your app can do is fall over.
[/quote]
OK. There are possible scenarios were the app can be downloading some significant amount of image data. I’ve had reports from people on it in the past. However, since moving to 64 bit, this has not happened. So I wasn’t sure if having this would do anything or not.
[quote]
This:
Dim bs as BinaryStream = BinaryStream.Open(f)
Will throw an IOException if the file cant be created or another error occurs. Without an exception handler thatll cause problems.[/quote]
Yes, I’ve fixed that. Others pointed that out as well!
Just because your app is 64-bit, doesnt mean that it cant run out of RAM. On a machine with > 4GB OF memory, and running nothing else, itll just take longer.
Remember all 64-bit does for you is remove the 4GB (3.5 on Windows) limit of the 32-bit pointers. Increased to something like 16TB, and at the rate we’re going that should be summer 2020.