Quantcast
Channel: daffodil Discussions Rss Feed
Viewing all 89 articles
Browse latest View live

New Post: VisualStudio vs SDK requirement

$
0
0
Thanks for your feedback.
I'm gonna ask operations to still support VS2005, and recommend developpers to use VS2010(/daffodil), and put some more effort in converting to the VS2010 crt/compiler

New Post: Error msb8020 after installing Daffodil on MsDev 2012 for vc80 tools

$
0
0
Hi,
I just installed Daffodil to use MsDev 2012 IDE with the vc80 toolchain that I already have. I'm getting
"Error 1 error MSB8020: The builds tools for v80 (Platform Toolset = 'v80') cannot be found. To build using the v80 build tools, either click the Project menu or right-click the solution, and then select "Update VC++ Projects...". Install v80 to build using the v80 build tools. C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V110\Microsoft.Cpp.Platform.targets 44 5 TaskManager

However I already have MsDev 2005 (VC80) on this machine and it is working fine. Msdev 2012 also has no issue building using VC110 tools.

I cleared my path, restarted the pc, reinstalled Daffodil and it still doesn't works.
I don't have MsDev2010 installed.

Does anyone knows how this can be fixed?

Thanks,
Louis

New Post: Error msb8020 after installing Daffodil on MsDev 2012 for vc80 tools

$
0
0
You must also install VS 2010 in order for the platform toolsets from older versions of VS to work.

New Post: MSB8020 when targeting v60 with Visual Studio/Visual C++ 6.0 installed

$
0
0
I receive a build error when targeting v60, even though I have Visual Studio 6 installed and can compile in the older IDE. I'm using the latest rev of daffodil with Visual Studio 2013 and Visual Studio 6 sp6.

New Post: MSB8020 when targeting v60 with Visual Studio/Visual C++ 6.0 installed

$
0
0
You need to have VS 2010 installed as well.

New Post: MSB8020 when targeting v60 with Visual Studio/Visual C++ 6.0 installed

$
0
0
Thanks missed that. I can compile fine now, however I can't debug.

Debugging information for '' cannot be found or does not match. Binary was not build with debug information.

<exe name>. Module was built without symbols.

Linker and debugger settings are correct. PDB gets created correct, but no joy.

New Post: MSB8020 when targeting v60 with Visual Studio/Visual C++ 6.0 installed

$
0
0
DEBUG -> Options and Settings -> General
Check "Use Managed Compatibility Mode"

New Post: Debugging information does not match, when using Visual C++ 6 compiler

$
0
0
Hi,
I have been using Daffodil with no problem in Visual Studio 2013, Windows 8.1 for a while.
Now I got a new Windows 10 machine, where I reinstalled Visual Studio 6, 2013 and Daffodil.

I am using v60 build tools, which compile fine the project.
However, when I try to debug, VS says that "debugging information does not match", but:
  • PDB file is there, same name of executable
  • Application built in Debug mode, with debug information enabled
  • Debugger works fine when using Visual Studio 2010 or 2013 build tools
  • Debugger works fine if opening the project inside Visual C++ 6 IDE.
I tried reinstalling all Visual Studio versions as well as Daffodil, but didn't solve.
Any clue what could the problem be?
Thank you very much in advance!!

New Post: Debugging information does not match, when using Visual C++ 6 compiler

$
0
0
Finally I actually found a working solution!

for VS2013:
Enable "Native Edit and Continue"
under Tools->Options->Debugging->Edit and Continue

for VS2015:
Enable "Use Native Compatibility Mode"
under Tools->Options->Debugging->General

New Post: Debugging information does not match, when using Visual C++ 6 compiler

$
0
0
Thanks for posting the solution.

New Post: TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

$
0
0
Hi,

I'm trying to compile with v80 (VS2005) in VS2012. I've installed VS2005 express, 2010 express and 2012 professional.

I've installed daffodil and I get the dropdown to select v80 as the Platform Toolset, but building gives me the error message:

TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

Looking at the "Microsoft.Cpp.Win32.v80.targets" file, it seems like it's looking for registry keys:
<VCInstallDir>$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Setup\VC@ProductDir)</VCInstallDir>
<VCInstallDir Condition="'$(VCInstallDir)' == ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0\Setup\VC@ProductDir) </VCInstallDir>
<VSInstallDir>$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Setup\VS@ProductDir)</VSInstallDir>
<VSInstallDir Condition="'$(VSInstallDir)' == ''">$(Registry:HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\8.0\Setup\VS@ProductDir)</VSInstallDir>
However, checking my registry, I don't have these keys. Is this why it's failing? I did a repair installation of VS2005 express and they don't appear, I even tried adding them manually, no joy. Am I on the right track?

New Post: TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

$
0
0
I think you're on the right track, but if VS 2005 Express did not include all the build tools, you may plug one hole only to find another. It's possible the directory structure is different, so you may also need to change hardcoded relative paths to the build tools in the VS 2005 installation.

New Post: TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

$
0
0
I probably also should have mentioned that I have VS 2005 installed on my D: drive, would that make any difference? Would you suggest i try to get a 2005 professional?

New Post: TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

$
0
0
I have managed to get to the next error message by manually including the 8.0 bin directory in the executables line.

For interest, this page says that the registry keys are different depending which version you have:

http://blogs.msdn.com/b/astebner/archive/2006/01/11/511887.aspx

Visual C++ 2005 Express - HKEY_LOCAL_MACHINE\Software\Microsoft\VCExpress\8.0\Setup\VS\ProductDir
Visual Studio 2005 Professional - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Setup\VS\Pro\ProductDir
Visual Studio 2005 Premier Partner Edition - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\Setup\VS\IDE\ProductDir

If you do not care which edition is installed, you can use the following registry value to detect whether or not any edition of Visual Studio 2005 is installed:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\SxS\VS7\8.0
8.0 is a REG_SZ value that specifies a fully qualified path to the Visual Studio 2005 root installation directory. By default, this value will be set to c:\Program Files\Microsoft Visual Studio 8, but will be different if the user has installed Visual Studio 2005 to a non-default path.

New Post: TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

$
0
0
Also could you double check this line is correct

<WindowsSdkDir Condition="'$(WindowsSdkDir)' == ''">$(VCInstallDir)PlatformSDK\</WindowsSdkDir>

On my 2005 Express install, there is no PlatformSDK folder inside the VC install directory. However in previous 2005 projects I've needed to include this path:

D:\Program Files\Microsoft Platform SDK

Which I installed separately I believe, as part of the Windows Server 2003 SP1 Platform SDK.

Which may be the same thing?

There is also this:

D:\Program Files (x86)\Microsoft Visual Studio 8\SDK\v2.0

New Post: TRACKER : error TRK0005: Failed to locate: "CL.exe". The system cannot find the file specified.

$
0
0
MichaelParker wrote:
Also could you double check this line is correct
<WindowsSdkDir Condition="'$(WindowsSdkDir)' == ''">$(VCInstallDir)PlatformSDK\</WindowsSdkDir>
Yes, it is correct.

New Post: VC6 builds but won't Debug - "binary was not built with debug information"

$
0
0
When I upgraded to Windows 10 last week I was pleased to find that the existing installation of VS6 did seem to work. That's to say it did build [1]. However on trying to debug something I found that although my application would run in the VC6 debugger, if I had a breakpoint it would break but not then be able to resume, or single step; all of these resulting in an "Access Violation" error (possibly followed by "Privileged Instruction").
I was very interested to find Daffodil, which I have installed and has allowed me to build my project using VC2013 with the VS6 tools. However, on attempting to run the project in the debugger I am being told "binary was not built with debug information".
I wonder if anyone else has had this working ? Or is there something incompatible between VS2013's debugger implementation and VC6's debug information ? Or have I just missed some configuration somewhere ? Or has Daffodil missed setting something ?


[1] It was on Win 7, which worked perfectly except for an issue where a process being debugged couldn't properly be stopped by the debugger (eg using shift-F5), leaving an orphaned process if that was tried, and needed to be stopped using Process Explorer.

New Post: VC6 builds but won't Debug - "binary was not built with debug information"

New Post: VC6 builds but won't Debug - "binary was not built with debug information"

$
0
0
Ok, seems I should have looked a little further through these discussions. It looks like it's already answered.

for VS2013:
Enable "Native Edit and Continue"
under Tools->Options->Debugging->Edit and Continue

Mine seems to be fixed by this.
Regards,
Richard.

New Post: When debugging VC6 code from within VS2015, "Microsoft Visual Studio Delay Notification" icon appears in the system tray and VS2015 becomes frozen.

$
0
0
Hi Owen,

I deeply appreciate your great job on making daffodil which saved our life and made a beautiful bridge to VS2015.

Currently I have an issue debugging a code written in VC6 and interfaced by VB6. When I attach the c++ code to the executable of this code which is generated by VB6, the "Microsoft Visual Studio Delay Notification" icon appears in the system tray and when I click on that, this message is shown:

"Microsoft Visual Studio is waiting for an internal operation to complete. If you regularly encounter this delay during normal usage, please report this problem to Microsoft."

The same code was fully working under VC6 IDE and I could attach it to the same process and put breakpoints and trace the code, but recently under VS2015, my breakpoints will not be hit and the system will get very slow and nothing happens except the mentioned message. Even the window for the executable file of this project will become kind of frozen.

Do you have any idea why this happens?

Kind Regards,
Masih
Viewing all 89 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>