I am using VisualStudio .NET 2003 on Windows 7. I get the error below while compiling one of my projects.
fatal error C1083: Cannot open include file: 'EXCHEXT.H': No such file or directory
The file EXCHEXT.h is supposed to be in C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\include folder. I have searched everywhere but cannot find this file.
Can anyone give me a pointer to what is happening?
I know it's been a while since the questions was posted, but kind of ran into this issue myself. I checked the windows SDK and, sure enough, it wasn't there. Seems to have been dropped a while ago, even though it is highly needed, for this type of addin development. I ended finding an old checked in copy I had, but also did come across this from google code: http://code.google.com/p/outcall/source/browse/trunk/exchange/include/EXCHEXT.H?r=8.
Hope this helps.
Related
I am new to programming windows MASM applications and from what I understand in order to call WinAPI functions I need to first include the appropriate .inc files.
I am using Visual Studio 2019 and I can't find anywhere on my system windows.inc files what so ever. I've
searched online and I couldn't find any SDK for x64 MASM.
This question was asked a while ago but the answer is only relevant for x32 assembly.
So I've been doing some digging and from what I understand there's no official SDK for x64 MASM which is weird. What I did find is this forum "The MASM Forum". And they are working on x64 MASM SDK for a while now but it has a lot of features.
They state it's not perfect but it's more than nothing.
I had trouble installing it to be honest, also my anti virus classified 2 of the files as Trojan so you should download the files at your own risk(Maybe do it on a VM ?).
Also the comments under the question suggested creating your own .inc files which from what I understand now is not that difficult, I will be trying both methods and keep this post updated on the results.
I'm not sure if you're still wanting an answer, probably not since this was asked almost a year ago, but I'll reply to help anyone who may also be wondering. I just started trying to learn MASM and I was having a lot of trouble setting everything up, in fact I'm still working on getting x86 to work correctly on an USB (I think masm32 must be at the root of the USB(note: for old version, updated version will be more like x64))
For x64 you'll need Visual Studio installed, I'm using VS 2022. My examples should give you a good idea, just change to match your specific set up.
ml64.exe, link.exe, and lib.exe are all in the same folder:
C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.31.31103\bin\Hostx64\x64\ml64.exe
The resource compiler, rc.exe, is in a different folder:
C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x64\rc.exe
I've run in to an issue where I can't build a freshly created C++/CLI Class Library project in Visual Studio:
Even though I haven't made any changes I get an error when I try to compile:
Severity Code Description Project File Line Suppression State
Error Could not load UI satellite dll 'FileTracker32UI.dll'. Make
sure it exists in an LCID subdirectory of 'C:\Program Files
(x86)\MSBuild\14.0\bin\'. TestProject c:\Users\abcde\documents\visual
studio 2015\Projects\TestProject\TestProject\FileTracker 1
I've created C++/CLI Class Library projects in the past on the same computer using Visual Studio 2015 without encountering this problem. Any idea what has gone wrong?
I ran into this strange issue today without making any code change. I suspect it appeared due to overnight windows update.
In my case , I copied the two files FileTracker32UI.dll and FileTracker64UI.dll
From
C:\Program Files (x86)\MSBuild\15.0\FileTracker\3082\
To
C:\Program Files (x86)\MSBuild\14.0\Bin\3082\
and it worked. My visual studio version is
Microsoft Visual Studio Community 2015
Version 14.0.25123.00 Update 2
I am hoping the info helps someone.
I had the exactly same problem, after some windows update by my IT.
According to the information (https://forum.dlang.org/post/ezuohezwuzyitjdzpfdw#forum.dlang.org), I renamed the file "FileTrackerUI.dll" to "FileTracker32UI.dll" in the latest LCID folder (latest numbered folder in same location)
Then, it worked at my PC.
Good luck
In my case it was a path issue. Using another directory (shorter path without special characters) solved the problem
I have Visual Studio 2010 SP1.
I wrongly edit and save the file
C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
and now I can't compile anymore.
The error I got is
1>C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.Targets(767,39):
error MSB4057: The target "_Xsd" does not exist in the project.
I reinstalled Visual Studio 2010, I copied the file from another computer but nothing works and I still have the same error. What can I do?
I search the solution on Internet and i found:
Copy the right target file from another machine to replace the target file.
Uninstall and re-install .Net Framework 4.0 and check if it works.
I tried to restore or install new version of the .NET framework, but other problems occured during installation maybe dued also by hardware problems (i got blue screen sometimes).
I know it isn't a good solution, but at the moment I solved the issue by formatting and reinstalling everything.
Background:
So I picked up Programming the Windows Driver model and tried to build the very first sample it has using visual studio 2013 Ultimate. While the book seems very reputed, there is no update for the sample code.
I saw some signs to used the older "build" instead of current msbuild / visual studio. But that is another learning I am not prepared to do unless required (especially as I didnt find nmake or build quickly enough and i ll be learning older build processes which I dont need to use).
Problem:
error C1083: Cannot open include file: '\inc\wxp\warning.h': No such file or directory stddcls.cpp
Building the sample gives me this error.
I included the folders for wdm.h and warning.h in the includes path. Wdm.h got resolved, but warning.h continues to throw an error - and I dont even know where warning.h in included/referenced.
I can post the entire code if required.
Yes, I am new to driver development.
If this book is too old to use, pointers to "newer" tutorials of Windows driver dev is appreciated.
In Visual studio
Project -> Properties -> C/C++ -> Advanced -> Forced Include file.
There is a hardlink to warning.h here. This needs to be changed to
C:\Program Files (x86)\Windows Kits\8.1\Include\shared\warning.h and the error goes away!
Another useful link for "Programming the Windows Driver Model" Oney:
http://csserver.evansville.edu/~reising/EE%20356%20Fall%202005/Changes%20to%20files%20from%20Walter%20Oney.pdf
I am trying to get started working with CUDA.
I fresh installed the trial version of VS2010 professional and downloaded the visual studio add on on NVIDIA's website (here )
I have a correct driver version installed, and the Nsight add on automatically installs the CUDA Toolkit.
Problem is, whatever CUDA project I try to compile, I always get this error :
1> Compiling CUDA source file kernel.cu...
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.2.targets(361,9): error MSB3686: Unable to create Xaml task. Compilation failed.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.2.targets(361,9): error MSB3686: Source file 'C:\Windows\TEMP\uq13nrom.0.cs' could not be found
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.2.targets(361,9): error MSB3686: No inputs specified
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.2.targets(361,9): error MSB3686:
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\BuildCustomizations\CUDA 4.2.targets(361,9): error MSB4036: The "CudaCompile" task was not found
Even when using the solutions provided in CUDA samples
I never used Visual Studio before, and I could not find ANY resource on the web related to this error.
I spent the whole day trying to fix it. I also tried to uninstall/reinstall everything; no success.
What drives me crazy is that right after the install my projects actually did build for an hour or two. And for a reason I can't explain, everything started failing.
I'd be really, really glad for any information you could give me. I don't see any other way to solve this.
So, I woke up this morning and directly got in front of the computer, a coffee in the hand, already expecting to spend the whole day just trying to get my tools working
. . . till I realized everything was working fine.
The very same code that leads to the error at midnight compiles just perfectly this morning .
The only difference ? Updates in Visual Studio.
Here is a screenshot of all the updates that have been applied during my sleep :
I bet one of those guys solved my problem, probably the .NET framework 4 related.
Hope this can help someone ;)
It has nothing to do with configuration. There is something messed up [by me/you] in the project setting file. I am facing this problem while updating an old project from CUDA 4.4 to CUDA 5.5. I tried modifying the old project file according to one of the new project files... changing build target and other related things................
New project is compile and executing, whereas, the old updating project lead me to this page. I'll update the thread with a solution later. Definitely, it is not .NET framework or any updates in my case
EDIT: I copied the .prop and other files from CUDA installation directory to Visual Studio directory and it started working again. Perhaps, I modified these files incorrectly.