Problem: I have old VB6 code, what is the easiest way to convert or port to VB.Net?

Solution:-

1. Copy the CLISMS folder (original code) into our local disk. 
2. Run the Visual Basic 2008. Click File>Open Project. It should appear like this. Open the CLISMS original code. 
3. Choose the project which is .vbp and click “Open”. 
4. Upgrade the coding using the upgrade wizard in VB.Net. It appear like this. Click “Next”. 
5. Choose “EXE”, click “Next”. 
6. Change to “CLISMS.NET”, click “Next”. 
7. Click “Yes”. 
8. Wait for the process porting to be completed. The dialog box will automatically closed once it is done. 
9. You can see the project has successfully ported. 

The following steps are optional.

1. Double click “My Project”, goto “Application”, change the “CLI” to “CLISMS”. Save it 
2. Click “Build -> Build CLISMS”.
    
3. Go to “G:\mobitek\CLISMS ori code\CLISMS.NET\bin” 
4. Copy the “sms.bat” from the ori code. 
5. Paste on your upgraded code. My path:G:\mobitek\CLISMS ori code\CLISMS.NET\bin
6. Right click the sms batch file and click edit.
7. It appear that can be edited one.The notepad appear. change the port number and change the telephone number. Then press ctrl+S.
8. Double click the sms batch file. It appear like this. Your cmd will automatically closed once the process of sending SMS is send. Then, it is done

Note: The clisms cant worked correctly if it situated on network folder. it must be copied into our local disk.

Reported by,
Iqa

Resources

• convert vb6 to vb.net 2008
• Upgrading from Visual Basic 6.0
• VIDEO — how to convert visual basic 6.0 to visual basic 2008 using visual studio 2008

Download user’s guide and software from here …

Step 1: DO NOT connect USB cable or connect modem to PC/server.

Step 2: Install the USB driver first by clicking on ‘run’. USB driver can be downloaded from here — https://www.mobitek.my/download/USB Drivers/USB Driver for MOBITEK S80.zip

Step 3: Click on ‘next’.

Step 4: Check the ‘I accept the terms in the License Agreement’ and click on ‘Next’.

Step 5: Choose the installation folder or path, then click on ‘Next’.

Step 6: Click on ‘Install’.

Step 7: Make sure to restart the machine or computer in order to use the installed driver.

Step 8: After computer is restarted, connect the modem to the computer. In device manager, the connected modem is listed as ‘Sierra Wireless AT Command Port (UMTS)’. In this example, the modem is connected to COM port number 29.

When connecting to a VNC Server (applies to both RealVNC and TightVNC), the VNC client (applies to both RealVNC and TightVNC) is unable to connect, and shows this message,  “Connection closed unexpectedly”.

The followings settings are properly configured and they are not the issues:-

• VNC server and client is allowed by firewall; and
• VNC port is correct;
• VNC password is correct.

However, the log file of TightVNC server shows:-

[ 2132/ 4332] 2016-06-15 13:23:30 ! write() function stopped because transport has not been initialized yet.
[ 2132/ 4332] 2016-06-15 13:23:32 ! AnonymousPipe::read() failed (m_hRead = 000000000000030C)
[ 2132/ 4332] 2016-06-15 13:23:32 ! The Pipe's read function failed after ReadFile calling (The pipe has been ended. (109))
[ 2132/ 4332] 2016-06-15 13:23:32 ! Exception during DesktopClientImpl creaion: 
[ 2132/ 4332] 2016-06-15 13:23:32 ! Error during RFB initialization: 
[ 2132/ 4332] 2016-06-15 13:23:32 ! Connection will be closed: 
[ 4500/ 4420] 2016-06-15 13:23:42 ! Desktop server application failed with error: The desktop server time out expired

The root caused is “RFB” on the VNC server.

Solution:-

• uninstalll “DisplayLink” driver from server and VNC client is able to connect to VNC server;
• uninstall any display driver that is incompatible with VNC server.

Another reason for “Connection closed unexpectedly” is that RealVNC version 4.x does not work in Windows 7. For Windows 7, it requires Real VNC version 5 and above.