![]() ![]() The procedures vary and sometimes can be costly. Net for example there are several tools that we use to lock an App from being easily decompiled. Net Is that, the modern solutions have learned and been cleaned from the passed weaknesses. The advantages of modern technologies over old ones in this case VB6 vs C#. All we do sometimes is to make that process a little more difficult. So there is nothing that cannot be decompiled. By this I mean is, you should be aware and agree that every code is crackable even native code can be cracked and it has been cracked even Microsoft, Adobe and Symantec agree to this. ![]() I hope this helps you.īefore I take you on this one, we need to come to the same level of understanding on this subject. Here is your code for the installer on the destination machine.Ī=array("your","list","separated","by","commas")Įnd subSet your application to start on sub main. I do no use crystal reports, I prefer vb datareport. MsgBox DLLServerPath & IIf(bRegister = True, "Registration", "Unregistration") + " Unsuccessful" 'MsgBox IIf(bRegister = True, "Registration", "Unregistration") + " Successful" Retval = CallWindowProc(pa, ByVal 0&, ByVal 0&, ByVal 0&, ByVal 0&) Pa = GetProcAddress(lb, "DllUnregisterServer") Pa = GetProcAddress(lb, "DllRegisterServer") Private Declare Function CallWindowProc Lib "user32" Alias "CallWindowProcA" (ByVal lpPrevWndFunc As Long, ByVal hWnd As Long, ByVal Msg As Any, ByVal wParam As Any, ByVal lParam As Any) As Long Private Declare Function GetProcAddress Lib "kernel32" (ByVal hModule As Long, ByVal lpProcName As String) As Long Private Declare Function LoadLibrary Lib "kernel32" Alias "LoadLibraryA" (ByVal lpLibFileName As String) As Long ![]() Private Declare Function FreeLibrary Lib "kernel32" (ByVal hLibModule As Long) As Long Having said that the bottom line is that VB6 is obsolete its time to start moving on. Some third party libraries that were shipped with VB6 and could be included during compilation may not be in the interest of Microsoft Support that too could bring serious issues in modern OS. There are more issues than that for example Data Connections(ODBC, ADO etc). Displaying a Form in Windows 7 and Windows 8 does not translate to full compatibility of VB6. A friend of mine had issues installing VB6 IDE on Windows 8 that's when I learned that The Visual Basic 6.0 IDE is no longer supported as of Apby MS. My Notify Icon on System Tray used to hang in Windows 7 and vista even when I exit the app but works well in Windows XP. Some of the issues I have had with my old VB6 app in Windows Vista and Windows 7 is sockets communication, I think this is due to hardened security in Vista and Win 7. ![]() I have had a lot of problems with my Old VB6 App and immediately switched to C Sharp the learning curve was rather tiring though, but now I am very comfortable. It has to be said that VB6 isn't fully compatible with Windows Vista and Windows 7 any other statement would be misleading. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |