I build 5 DLLS and my exe in C#.Net 2.0 with ILMerge to one exe file.
The problem is that now every time I start the output exe, an empty command prompt opened with the exe. Anyone knows the problem and know how to solve it?
I found answer. The output parameter is "winexe", don't "exe". Me is it solve the problem.
Related
I want to use this project face_eye_detection.zip.
When I run it I get an error 'library failed to load',
So I changed the dll link
but the problem remains the same, I even change the dll link and it doesn't work.
Where exactly is the problem? In the link above, the program worked well with the others
Double check that it is a c++ dll and not a dotnet dll, that one has got me before.
I have a WiX installer that was working fine, but it's been a few months since I worked on it... so, I am not attempting to build the installer (on a reconfigured machine) and now it fails to build every time. I've tried to simplify everything to isolate where it's failing, but I still can't seem to figure out why. Essentially, it looks like it's failing at the pre-build process. I had a length Pre-build Event command, but I've simplified it to the bare essentials. Here's my command:
call “$(WIX)bin\heat.exe” dir "$(SolutionDir)MyProj\bin\Release" -out “$(ProjectDir)MyFiles.wxs”
The error I'm getting is:
call “C:\Program Files (x86)\WiX Toolset v3.10\bin\heat.exe” dir "C:\Users\MyName\Documents\GitHub\MyProj\bin\Release" -out “C:\Users\MyName\Documents\GitHub\MyProj\Installer\MyFiles.wxs”
The filename, directory name, or volume label syntax is incorrect.
The code appears to exit with code 1, which seems to suggest that it's failing to locate a filename or path... however, I've checked the paths that are printed in the output log and the heat.exe application does exists under the C:\Program Files (x86) directory. The directory (dir) it's trying to harvest is properly defined and the output location is as well. So, does anyone know why this is failing?
Update
What's incredibly strange is that the pre-build event command seems to fail even when I simplify the command to try to simply call the heat.exe application (with no other parameters). I tried changing my pre-build event to the following:
call “C:\Program Files (x86)\WiX Toolset v3.10\bin\heat.exe”
As you can see from the attached image, the heat.exe application is indeed located in the directory specified in the build command. Yet, I still get an error saying that the MSBuild failed and exited with code 1. If I check the output log, it says that the, "filename, directory name, or volume label syntax is incorrect". However, I can say that this installer was working properly a few months ago with no changes to the build events... so I really don't know why it wouldn't work now, except that I had to reconfigure my machine and reinstall Windows 10 recently. I downloaded and installed the latest WiX toolset, and would assume that would be everything that is needed. But, this error persists. Any ideas?
This is really dumb but I believe you need to put a \ at the end of your dir IIRC. I think I ran into the same issue at one point. The error is not particularly helpful.
call "$(WIX)bin\heat.exe" dir "$(SolutionDir)MyProj\bin\Release\" -out "$(ProjectDir)MyFiles.wxs"
(I think I was remembering backwards and you need to NOT have the trailing \ in the dir.. sorry)
Just in case you can't get the pre-build event to work, you can also call heat like this (requires editing the wixproj file)
<Target Name="BeforeBuild">
<Exec Command=""$(WIX)bin\heat.exe" dir "$(SolutionDir)MyProj\bin\Release" -out "$(ProjectDir)MyFiles.wxs""/>
</Target>
This is how I call heat in some of the installers I've authored. If this also doesn't work I'm out of ideas for why this doesn't work for you.
I know its a little old question but I've faced the issue and spent hours to notice different qoutes here: “$(WIX)bin\heat.exe”. Replace with straight ones "$(WIX)bin\heat.exe" and enjoy.
I was using my command line on my Windows 8 pc, after I typed the ls command, then I got the following error:
ls.exe-System Error
The program can't start because cygintl-2.dll is missing from your computer. Try reinstalling the program to fix this problem.
Actually, I have googled it and watched some vids, I have tried download a cygintl-2.dll zip file, then extracted the dll file then copy it to the system32 folder. However, it still display the error. I also tried to reinstall the Microsoft Visual C++ Redistributable. it was failed also. I have no idea where I can find any help about this. Hope anyone can help me. Many Thanks!!!
It is because of the lack of cygintl-2.dll&cygintl-1.dll in OpenSSH/bin.
try finding and downloading the two dlls then copy them into OpenSSH/bin (usually it is installed in /program files/openssh/bin, or you can check the environment path to find the installation path)
I installed a newer version of OpenSSH and it fixed the problem thankfully. I was getting pretty worried! Specifically, I followed these two links (https://answers.microsoft.com/en-us/windows/forum/windows_7-performance/lsexe-system-error-how-to-browse-directories/2dddf4a5-5958-4768-acd7-ab4cf816f57e?auth=1 and https://sourceforge.net/p/sshwindows/bugs/2/) and then installed the executable from this site: http://sshwindows.webheat.co.uk/
I am trying to build a program for x64, but I keep getting the following error messages:
C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(2554,5): error MSB4216: Could not run the "GenerateResource" task because MSBuild could not create or connect to a task host with runtime "CLR4" and architecture "x64". Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "C:\Program Files (x86)\MSBuild\12.0\bin\amd64\MSBuild.exe" exists and can be run.
C:\Program Files (x86)\MSBuild\12.0\bin\Microsoft.Common.CurrentVersion.targets(2575,7): error MSB4028: The "GenerateResource" task's outputs could not be retrieved from the "FilesWritten" parameter. Object does not match target type.
MSBuild.exe exists and can be run, so I don't know why I am getting these errors.
I am using Visual Basic in Visual Studio Professional 2013 (Update 4). I am not using any DLLs, all I am creating is a standalone .exe file.
I've tried searching, both here and on Google, but cannot find anything helpful. Then again, I have a tendency to overlook things, so the answer has probably been screaming in my face for the last hour. I apologise in advance if this turns out to be the case.
Any and all help is very much appreciated.
replace
C:\Program Files (x86)\MSBuild\12.0\bin\amd64\MSBuild.exe
by
C:\Program Files (x86)\MSBuild\12.0\Bin\MSBuild.exe
and try.it should do some difference.this occurs because the version on msBuild.exe has changed after update4 of vs2013.check for version differences..
also i suspect you are trying to build the solution in x86 architecture.if first solution doesnt work,go to the Build tab, change the Platform target from Any CPU" to "x86" and try. hope it helps.
I just encountered this exact same error in a multiple project VB solution when trying to start a debug instance of one project. By forcing a rebuild of that one project I was able to fix the issue and start the debug instance.
I solved this problem by opening the project in Visual Studio 2017, instead of 2015
I've implemented the MSBuild Community Tasks from tigris to my C# Project.
My Problem is that im not alone working on this project, but i dont want everyone to install the MSBuild Community Task on his local PC.
Without MSBuild Community Task you're not able to compile the project.
So my idea was to make a small workaround, i want to include the Install-Files to my project and copy it with a precompile-command to the MSI-Install-destination
But i dont know where the MSI saves its files.
Does anyone know how to find out where the MSI File copies the included file to?
Or does anyone have a better idea?
Thanks, Alex
It solved my problem executing the MSI-File with the command-shell, I've changed the TargetDir to C:\Temp\MyMSI and the generated folder-structure told my where it's saving the files to.
msiexec /a "MyMsi.msi" /qn
TARGETDIR=C:\Temp\MyMSI