The first one is just a warning and you can workaround it by going to the designer.prg file where "components" is declared and change the declaration from
PRIVATE components AS System.ComponentModel.IContainer
to (just add the assignment)
PRIVATE components := NULL AS System.ComponentModel.IContainer
About the second thing, can you please check that the reference to VulcanVORDDClasses.dll still exists in your project references? If it does, then you probably just need to go to the Project settings, in the Language page and enable the option "Enable Implicit Namespace lookup".
In October 2018 I ported the Vulcan app to XSharp, the client installation was OK and the app worked well.
Build with the current XSharp version at that time.
It was necessary to make some update in the application. After build the application in my computer(with Win10) work OK.
In customer computer does not start. It appears in Task Manager and closes after a few seconds without any error message.
Customer have a HP ProDesk 400 with Windows 7 Profesional.
Versions Windows, .Net ,Visual Studio and XSharp are attached.
The problem is only with the application in Vulcan dialect , the test app in Core dialect runs fine.
Thanks, unfortunately this did not give much info, but as I explained by PM, the problem is most likely a (vulcan) dll mismatch, please check what I told you in private. Also make sure the customer is not running your app from a network drive. (it is possible to do that, but he will need to provide specific rights to the app/folder to do that).
after change VulcanRT and VulcanRTFunc from 3.0....... to 2.0... in project and rebuild, aplication work ok. Thank you for your advice.
It would be possible to replace the Vulcan runtime for the XSharp runtime in this project in order to exclude runtime issues in the future?
OK, great to hear it's all working now! Yes, of course you can use the X# runtime instead of the vulcan one (especially since from what I see you do not use any dbf stuff), but still you will need to be distributing the same X# dlls that you used for compilation (there are new versions if X# dlls with each new build).
In order to do it, remove the references to VulcanRT and VulcanRTFuncs and then add references to XSharp.Core, XSharp.RT and XSharp.VO. Normally, your app should still compile without any code changes after doing that, but please make enough testing of your app's behavior at runtime to make sure it works as before. The X# runtime is already mature enough and is used by several people already in production, but possibly some incompatibility with the vulcan one has crept in somewhere, so better give your app a good test with it, to be sure.