JamieNavarro Posted July 18, 2017 Report Share Posted July 18, 2017 Hello, I was directed by John Browne to post my issue here, so here it goes... The below pertains to a Windows XP Professional 32-bit virtual machine with 1.5GB RAM (VirtualBox v5.0.26 r108824). The host machine is Windows 10 Professional (not sure if that matters, but there you go). I'm having an issue with Step 4 - when I first ran it, I didn't notice that the 'Target Language' was set to 'CSharp', so I ran it as is, and everything seemed to have gone fine. However, at some point shortly thereafter, I realized that it was set to CSharp…but I want 'Visual Basic'. I started all over and tried it again, but this time set that option to 'Visual Basic'. It seemed to have worked, but at the very end it gave me an error message (screenshot attached). I closed out VBUC, reopened and tried to run it again, with Visual Basic selected, and got the same exact error at the same point - the very end. I tried again, but left CSharp selected, no error. So there's something definitely about the 'Visual Basic' option that it's not liking. I also attached my VBUMLOGFILE.log file. I'd be happy to provide any more information that you guys may require. VBUC Error.bmp VBUMLOGFILE.log Link to comment Share on other sites More sharing options...
Mobilize.Net Staff OlmanQuesada Posted July 19, 2017 Mobilize.Net Staff Report Share Posted July 19, 2017 (edited) Hi Jamie, Could be that possible for you to share with us additional information about variables/properties declared in this form:SGIInvoicing.frmSGIInvoicing. In addition, please try migrating the application to Visual Basic .Net by setting the "Helpers Integration" option to "Source Code" rather than "Binary". regards, OlmanQ Edited July 19, 2017 by OlmanQuesada Link to comment Share on other sites More sharing options...
JamieNavarro Posted July 20, 2017 Author Report Share Posted July 20, 2017 Hi Olman, Thanks for the reply! I did what you said - changed the option from 'Binary' to 'Source Code', and no crash! I never noticed it but when I change the Target Language to Visual Basic, that option automatically changes to 'Binary'. I don't know what it's for so I didn't pay much attention to that option. So I assume you don't need more information about frmSGIInvoicing, but if you do, I actually sent a link to the VB6 project via Dropbox to John Browne a couple days ago...maybe he can share it with you? Or I can send you your own invitation if you want. Does this mean that we don't need to do the meeting with Robert tomorrow morning after all? Or was it going to be for getting the upgraded code working? Thanks a bunch, Jamie Link to comment Share on other sites More sharing options...
Mobilize.Net Staff OlmanQuesada Posted August 7, 2017 Mobilize.Net Staff Report Share Posted August 7, 2017 Hi Jamie, Sorry for the delay. The Helpers are written in C#, so when the code is migrated to VB.Net, the VBUC switches the "Helper Integration" option to binary, but you can change it back to "Source Code". We've found the error is not present when the code is converted to a newer version of VS.Net (like 2013/2015). Regards, Olman Q Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now