![]() ![]() Then you don't have to worry about it again. Personally I find the first approach easier. You can then set and hitīreakpoints in the normal way you're used to.Īlternately you can also do this using Tools->Attach to process, but vbp file in the command lineĪrguments (also with quotes around it). Select this option and type in "C:\Program Files\Microsoft VisualĪfter that, put the full path to your. If you double-click My Project in Solution Explorer and go to theĭebug tab you'll see an option that says "Start External Program." ![]() I am not sure you can do it or not, but I have gotten some ideas from following link: Once you debug the debugger will stop on those lines of code.ĭisclaimer: I have not tried this myself. files in VS.NET and you can put breakpoints in the file. PDB file is that was generated in step 1. Select the properties.Īdd to the “Debug Source Files” an entry that points to the path where the source code is for the VB6 component.Īdd to the “Debug Symbols Files” an entry that points to the folder where the. Go to the project properties and select the “Configuration Properties->Debugging” property page and enable unmanaged debugging.įor VB.NET projects this option is “Unmanaged code debugging” and for C# is “enable unmanaged debugging.” 3. (Make sure you have binary compatibility on your VB6 dll set or you’ll have to drop and re-add your reference to the VB6 component in VS.NET.) 2. ![]() This file contains the debugging information so the VS.NET debugger can line up source and hit breakpoints, etc. PDB (Program Database) file along with your. In VB6 open up your vbp file and goto “Project->Properties.” Select the “compile” tab and check “Compile to Native Code.” Then select the “No Optimization” radio button and check “Create Symbolic Debug Info.” ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |