Visual Basic Build Error
-
I have a Visual Basic 6 project when I update in the form of the project then run the application from inside the Visual Studio 6 every thing goes fine. When I build "Make" the exe the Visual basic ignore all my code updates and the exe appear as if I didn't change any thing. Any Idea !!!!
-
I have a Visual Basic 6 project when I update in the form of the project then run the application from inside the Visual Studio 6 every thing goes fine. When I build "Make" the exe the Visual basic ignore all my code updates and the exe appear as if I didn't change any thing. Any Idea !!!!
I would try deleting or renaming the previous executable and "Make" it again. That should get you the latest build with the latest changes. If all else fails why not try .NET. Just a thought.
-
I have a Visual Basic 6 project when I update in the form of the project then run the application from inside the Visual Studio 6 every thing goes fine. When I build "Make" the exe the Visual basic ignore all my code updates and the exe appear as if I didn't change any thing. Any Idea !!!!
-
I have a Visual Basic 6 project when I update in the form of the project then run the application from inside the Visual Studio 6 every thing goes fine. When I build "Make" the exe the Visual basic ignore all my code updates and the exe appear as if I didn't change any thing. Any Idea !!!!
hi, i would try to register the .exe first and then expect the changes to appear IF running it from outside of Visual Studio
-
hi, i would try to register the .exe first and then expect the changes to appear IF running it from outside of Visual Studio
Thank you. The exe was designed to be called from the Run tool and pass some parameters as argument to it. By mistake I renamed the exe and put a space in its new name. then I figured out that the run command utility doesn't support having space in the exe name and kept calling old exe
-
I would try deleting or renaming the previous executable and "Make" it again. That should get you the latest build with the latest changes. If all else fails why not try .NET. Just a thought.
-
This hint helped me to find the issue. By some reason I kept calling old exe version rather than the new compiled one
I am glad that helped. I have done that same exact thing. :)