I'm trying to make an installer for Windows with WiX. I'm following this tutorial.
I get the following error:
trunk\Setup\Product.wxs(12): error LGH
T0094: Unresolved reference to symbol 'WixUI:WixUI_InstallDir' in section 'Prod
uct:*'. [trunk\Setup.wixproj]
Here is my Product.wxs and my setup.build file.
Thanks!
Related
I'm compiling a kernel mode driver that uses the Microsoft Dmf framework (DmfK.lib)
After the last Visual Studio update some strange linker errors appeared :
EmulationTargetPDO.obj : error LNK2019: unresolved external symbol __stdio_common_vswprintf referenced in function _vsnwprintf_l
Utilities.lib(savedata.obj) : error LNK2001: unresolved external symbol __stdio_common_vswprintf
DmfK.lib(DmfUtility.obj) : error LNK2001: unresolved external symbol __stdio_common_vswprintf
EmulationTargetPDO.obj : error LNK2019: unresolved external symbol __stdio_common_vsprintf referenced in function _vsnprintf_l
DmfK.lib(DmfCore.obj) : error LNK2001: unresolved external symbol __stdio_common_vsprintf
DmfK.lib(Dmf_CrashDump.obj) : error LNK2019: unresolved external symbol __stdio_common_vsprintf_s referenced in function _vsprintf_s_l
Here's the software and kits versions I use (shown in VS "About" windows):
Microsoft Visual Studio Professional 2019 Version 16.10.0
Windows SDK 10.0.19041.685
Windows Driver Kit 10.0.19030.1000
The second strange thing is that I've downloaded and installed the WDK 10.0.19041.685 but VS still displays 10.0.19030.1000 ...
A similar problem can be found here : Linker error when compiling windows kernel mode driver x64 but it hasn't been solved.
Set this define before including any headers:
#define _NO_CRT_STDIO_INLINE
or add it to the compiler's command line:
-D_NO_CRT_STDIO_INLINE
We (Microsoft driver team) are looking into this issue to see about removing the need for such a workaround.
I get a build error using Visual Studio for Mac with an iOS project. It also occurs in an Android project on Mac and in an iOS project in Visual Studio 2019 on Windows 10.
I was able to run the project when on an iPhone 8 when it was "clean", before I put any code in it.
Here is the error:
/Users/shinehah/VSProjects/iOSAppSpeechToText01/iOSAppSpeechToText01/MTOUCH: Error MT0009: Error while loading assemblies: /Users/shinehah/.nuget/packages/grpc.core/1.18.0/runtimes/win/native/grpc_csharp_ext.x64.dll (MT0009) (iOSAppSpeechToText01)
Here are the warnings:
/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/Current/bin/Microsoft.Common.CurrentVersion.targets(5,5): Warning MSB3277: Found conflicts between different versions of "System.Numerics" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. (MSB3277) (iOSAppSpeechToText01)
/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/Current/bin/Microsoft.Common.CurrentVersion.targets(5,5): Warning MSB3277: Found conflicts between different versions of "Microsoft.CSharp" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. (MSB3277) (iOSAppSpeechToText01)
/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/Current/bin/Microsoft.Common.CurrentVersion.targets(5,5): Warning MSB3277: Found conflicts between different versions of "System.Net.Http" that could not be resolved. These reference conflicts are listed in the build log when log verbosity is set to detailed. (MSB3277) (iOSAppSpeechToText01)
/Library/Frameworks/Mono.framework/Versions/5.18.1/lib/mono/msbuild/Current/bin/Microsoft.Common.CurrentVersion.targets(5,5): Warning MSB3276: Found conflicts between different versions of the same dependent assembly. Please set the "AutoGenerateBindingRedirects" property to true in the project file. For more information, see http://go.microsoft.com/fwlink/?LinkId=294190. (MSB3276) (iOSAppSpeechToText01)
/Users/shinehah/VSProjects/iOSAppSpeechToText01/iOSAppSpeechToText01/ViewController.cs(33,33): Warning CS1701: Assuming assembly reference 'Google.Protobuf, Version=3.4.1.0, Culture=neutral, PublicKeyToken=a7d26565bac4d604' used by 'Google.LongRunning' matches identity 'Google.Protobuf, Version=3.5.1.0, Culture=neutral, PublicKeyToken=a7d26565bac4d604' of 'Google.Protobuf', you may need to supply runtime policy (CS1701) (iOSAppSpeechToText01)
/Users/shinehah/VSProjects/iOSAppSpeechToText01/iOSAppSpeechToText01/ViewController.cs(29,29): Warning CS1701: Assuming assembly reference 'Google.Protobuf, Version=3.4.1.0, Culture=neutral, PublicKeyToken=a7d26565bac4d604' used by 'Google.LongRunning' matches identity 'Google.Protobuf, Version=3.5.1.0, Culture=neutral, PublicKeyToken=a7d26565bac4d604' of 'Google.Protobuf', you may need to supply runtime policy (CS1701) (iOSAppSpeechToText01)
The error occurs last, after the warnings.
I didn't add any code whatsoever. The only difference is that I installed Google.Cloud.Speech.V1.
That's everything I changed after a new clean project.
I have tried using Google.Cloud.Speech.V1 1.0.1 package instead of 1.1.0, but I get the same error.
I got a lot of errors as below with my database project, Visual Studio 2013. However I don't use any of below dlls anymore (I used them before, but I removed them from references).
Error SQL72009: [Accessibility] has an unresolved dependency to
[System.Windows.Forms]. A deployment script with correct ordering cannot be
created.
Error SQL72009: [System.Design] has an unresolved dependency to [System.Web].
A deployment script with correct ordering cannot be created.
Error SQL72009: [System.Windows.Forms] has an unresolved dependency to
[System.Web]. A deployment script with correct ordering cannot be created.
Error SQL72009: [System.Windows.Forms] has an unresolved dependency to
[System.Design]. A deployment script with correct ordering cannot be created.
Error SQL72009: [System.Windows.Forms] has an unresolved dependency to
[System.Drawing.Design]. A deployment script with correct ordering cannot be
created.
Error SQL72009: [System.Windows.Forms] has an unresolved dependency to
[Microsoft.Build.Tasks.v4.0]. A deployment script with correct ordering cannot
be created.
....
So my question is:
What exactly does error sql72009 mean?
When does it happen?
I just ran into this problem using SQL Server Data Tools, and in my case, the problem was a circular dependency: two functions referenced each other.
I have a C++ Visual Studio 2010 project, which I can run in x64 mode. But I want to run it in x32 also.. So here I have a problem - this project uses a Matlab API, which I never met before. I have these errors:
1>ReadMatrix.obj : error LNK2001: unresolved external symbol _matOpen
1>ReadMatrix.obj : error LNK2001: unresolved external symbol _matGetVariable
1>ReadMatrix.obj : error LNK2001: unresolved external symbol _mxGetDimensions_730
1>ReadMatrix.obj : error LNK2001: unresolved external symbol _mxGetPr
1>ReadMatrix.obj : error LNK2001: unresolved external symbol _mxDestroyArray
1>ReadMatrix.obj : error LNK2001: unresolved external symbol _matClose
I looked in the Matlab folder(2011a) on the path
..\MATLAB\R2011a\extern\include, but found there only x64 files. What I should do?
You'll have to get hands on the 32bit libraries from a corresponding 32bit Matlab installation.
One possible simplification:
For compilation (not running) only, you do not necessarily need a full 32bit MATLAB installation, but only the library files (libmat, libmx, libmex).
This might simplify things if you'd e.g. like to compile the 32bit version for a colleague etc.
Following on from my previous question regarding debugging of native code, I decided to create a simple test from a console app as I wasn't getting anywhere with debugging the service directly.
So I created a vc6 console app, added the dll project to the workspace and ran it.
Instead of executing as expected it spat out the following linker errors:
main.obj : error LNK2001: unresolved external symbol "int __stdcall hmDocumentLAdd(char *,char *,long,char *,char *,long,long,long,long *)" (?hmDocumentLAdd##YGHPAD0J00JJJPAJ#Z)
main.obj : error LNK2001: unresolved external symbol "int __stdcall hmGetDocBasePath(char *,long)" (?hmGetDocBasePath##YGHPADJ#Z)
Debug/HazManTest.exe : fatal error LNK1120: 2 unresolved externals
This seems to be a simple case of forgetting something in the linker options: However everything seems to be normal, and the lib file, dll and source is available. If I change the lib file to load to nonsense it kicks up the fatal error LNK1104: cannot open file "asdf.lib", so that isn't a problem.
I have previously linked to dll and they have just worked, so what I have forgotton to do?
Update: As per this thread I looked to see if I could find out any additional information. This is what dumpbin from VS2005 gives me.
> dumpbin /linkermember Hazardman.lib | findstr "DocumentLAdd"
F6DC __imp__hmDocumentLAdd#36
F6DC _hmDocumentLAdd#36
5B __imp__hmDocumentLAdd#36
5B _hmDocumentLAdd#36
Then running it through undname results in:
> undname ?_hmDocumentLAdd#36
Microsoft (R) C++ Name Undecorator
Copyright (C) Microsoft Corporation. All rights reserved.
Undecoration of :- "?_hmDocumentLAdd#36"
is :- "?_hmDocumentLAdd#36"
Which is wrong. If I put in the mangled name from the IDE it gives the lot better result of:
> undname ?hmDocumentLAdd##YGHPAD0J00JJJPAJ#Z
Microsoft (R) C++ Name Undecorator
Copyright (C) Microsoft Corporation. All rights reserved.
Undecoration of :- "?hmDocumentLAdd##YGHPAD0J00JJJPAJ#Z"
is :- "int __stdcall hmDocumentLAdd(char *,char *,long,char *,char *,long,long,l
ong,long *)"
Now I have this information, what can I do with it? It seems from this Raymond Chen article I can manually fix it but tweaking an option, but my I can't discern from my results what option is needed (is there an 'ignore all parameters' checkbox?!).
So it seems that it is looking for non-existant functions or the parameters of the function have been left off (or dumpbin doesn't like VC6 libs), but it stil doesn't get me nearer my goal of fixing my problem.
Are you using the correct calling convention?
Your library appears to use stdcall. Maybe your test code is using cdecl (appears to be the default).
According to this page, the linker name decorations differ between the caling conventions so this can explain the symptoms you are seeing.