Welcome to our forums
I think, when i originally installed the upgrade to v6.3 I didn't opt for the VS integration. So, I'm trying to rerun the installer but I only get the option to remove FTN95!
Help!
K
Hmmm, so i went with 'remove', then a reinstall, but the 'integration with VS' options are all greyed out?
Help!
K
Presumably VS is already fully installed before you reinstall FTN95.
yep, but opening VS only gives me VC++ as a project option? How do I add in FTN95 files?
K
EDIT: aah, i may only have vc++ studio express installed, but there's a link to a 90-day trial of 2010 professional...
You should be able to use VS express but only when dedicated to FTN95 (unless you trick VS in some way).
Look at the Silverfrost main website to see if there are special instructions for installing the two together.
the website refers to 'plugins', how do i find/implement them?
http://www.silverfrost.com/46/ftn95/ftn95_and_visual_studio.aspx
K
The following link leads to a download for both FTN95 and VS Express together....
but will that interfere with my existing 'full copy' of FTN95?
K
Probably not because your licencing information should not be deleted with the new install. However, you should backup your existing FTN95 and/or install to a different folder or a different machine.
OK, making some progress, but stumbling over a couple of things:
1 The installer doesn't give the option to 'not load' the FTN95 express compiler (RH click at the relevant stage does nothing)
2 So, i've just gone ahead with the full install...
3 ...and I've loaded up a couple of source files and compiled them, but, I can't see where, in the IDE, to specify where the build process should search for DLLs to satisfy external references?
K
edit:
4 Trying to attach the IDE to a running process results in an error:
'unable to attach to the process. MSPDB80.dll cannot be loaded'
Have you looked at 'References' in the Project Explorer window?
Quoted from PaulLaidler Have you looked at 'References' in the Project Explorer window?
I hadn't, but I have now! 😃
K
Getting closer...
What I am trying to do is debug into a FTN95 DLL, that is linked against a 3rd party exe. I run the exe, kick off the DLL, then try to attach the process to the VS debugger. But my breakpoints turn 'inactive', with a tooltip of
'no symbols have been loaded for this document'.
I'm running in 'debug mode'. The compiler switches are '/debug /full_debug /P6 /fpp'
what else do I need to do?
K
You will usually need to have debugging code built into the exe as well as the dll. However, if everything is set up right, you should be able to open a dll source file and then set a break point within it.
Quoted from PaulLaidler You will usually need to have debugging code built into the exe as well as the dll. However, if everything is set up right, you should be able to open a dll source file and then set a break point within it.
I can set the breakpoints OK, but when I attach to the process, they go 'inactive'. I'll see if I can get a 'debuggable' exe...
Tks.
K
Quoted from PaulLaidler You will usually need to have debugging code built into the exe as well as the dll. However, if everything is set up right, you should be able to open a dll source file and then set a break point within it.
Apparently, I need to generate a .PDB file but I can't see what option to set to create one?
K
Quoted from KennyT
Quoted from PaulLaidler You will usually need to have debugging code built into the exe as well as the dll. However, if everything is set up right, you should be able to open a dll source file and then set a break point within it.
Apparently, I need to generate a .PDB file but I can't see what option to set to create one?
K
this is the listing I get:
Command line for link:
slink.exe -EXPORTALL -debug -DLL -OUT:'Debug\\Win32\\Senergy.dll' @'C:\\Users\\kenny\\Documents\\Silverfrost FTN95 Express\\Senergy\\Senergy\\link.lst' 'C:\\duk6\\app_main.dll' 'C:\\duk6\\dukpet.dll' 'C:\\duk6\\llib.dll' 'C:\\Program Files\\IntPetro41\\PGL.IP.API.NativeExports.dll' 'C:\\Windows\\Microsoft.NET\\Framework\\v2.0.50727\\System.dll' 'C:\\Windows\\Microsoft.NET\\Framework\\v2.0.50727\\System.Data.dll' 'C:\\Windows\\Microsoft.NET\\Framework\\v2.0.50727\\System.XML.dll'
Linker output:
WARNING - Default LibMain being provided
Creating dynamic link library: Debug\\Win32\\Senergy.dll
Senergy build succeeded.
Given that it's using 'SLINK', is there an option to produce a PDB file (I can't see one in the help for SLINK) or can I specify another linker using the same OBJ files?
K
If you are not using .NET then you can use SDBG directly to run the debugger. This provides an alternative to debugging within Visual Studio.
From SDBG you could try stepping into the main program and then open a source file for your DLL(from SDBG) and set a break point in the file. I think this might work but, if I have tried this, it was a long time ago.
If this works from SDBG then you might find that you can do the same thing from Visual Studio.
Quoted from PaulLaidler If you are not using .NET then you can use SDBG directly to run the debugger. This provides an alternative to debugging within Visual Studio.
From SDBG you could try stepping into the main program and then open a source file for your DLL(from SDBG) and set a break point in the file. I think this might work but, if I have tried this, it was a long time ago.
If this works from SDBG then you might find that you can do the same thing from Visual Studio.
Hmmm,
The EXE I'm linking my DLL to is .NET. I've got past some 'exceptions' by setting the 'ignoreException' values in my SDBG.INI file but after initialising the app, it exits with a code 99936666.
K
Your exe and dll must be both .NET or both Win32.