I have VS17 installed and have been studying C# for a while. Ever since I began, I was asked to run the ildasm.exe application, but that didn't work since in my Visual Stidio Command Prompt, when I type ildasm or ildasm.exe, it just says that the command doesn't exist.
I was able to curb that by adding the ildasm.exe application directly to the "Tools" menu of VS17 and accessing it from there and I also copied the path to the "Environment path" so that I could access it through PowerShell directly.
But now I'm being asked to access another application called dumpbin.exe, which has the same problem I initially had with ildasm.exe in the Visual Command Prompt, but this one I simply can't find the path in order to access it and I've googled and searched this website in search of the path, but I only found it for older versions of VS, which were of no use and running a search through my machine I wasn't able to find it either.
Can anyone help me find what is wrong with my Visual Command Prompt that makes these commands not available?l
With proper installation of VS you should have no problem with running Developer Command Prompt for VS 2017 and access all the commands from there.
So maybe you should check it if there are no issues there.
With DUMPBIN there might be a different case. It is part of C/C++ Build tools so you might not have them installed. Open the VS installer and check if you have this part on your machine.
And the path that this tool is installed is:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\VC\Tools\MSVC\14.10.25017\bin\HostX86\x86\dumpbin.exe
Related
I’m trying to automate an installation for an exe file, I can’t use any tools. Already tried /s, extracting the files, and using visual studio.
My company developed two install shield apps that I’m trying to make an automated installation to, I’m having trouble with one.
Neither apps have switches, I tried /s /qn /silent /verysilent , none worked.
I found a solution for the first app, I used - filepath.exe /s/x /b”C:/NewLocation” /v”/qn” , which transformed the exe file into an msi and then I used the msi to silent install, but this doesn’t work on the second exe file.
I tried these:
-looking for switches (filepath.exe /?), it has none.
-extracting the files in the exe w 7zip, there’s two Msi’s in it but both of them don’t include the whole installation.
-using visual studio (c#) and starting a process, with createNoWindow=true n
The main issue is that my company works on a separate network which is not connected to the internet, so I can’t use any tools from it.
Is there any command/code or any way to automate this installation?
I've been trying to run a C# project in Visual Studio and keep getting hit with the error:
'"dotnet.exe"' is not recognized as an internal or external command,
operable program or batch file.
From what I've seen online, several people have managed to fix this by messing around with the SDK or with the 'path' environment variables in Window's System properties tab. The problem is, I have no idea what any of these system settings and specifications do, and I can't get a clear answer.
I can tell that VS isn't able to get dotnet working, so what ideas come to mind to fix this error?
Install the DotNet Core Runtime or SDK (I use latest version)
The SDK has all the tools needed for development (including the runtime), while the Runtime is needed for running dotnet core applications.
After installation, you will need to restart the PC yourself so that the data entered in the PATH variable are available
Runtime link
Check if you have %ProgramFiles%\dotnet\ folder in your PC, that's where the dotnet.exe file should be.
If you found none, that mean you have not installed .NET Core SDK/Runtime. As you have VS, I am assuming you are writing some code with it, you should install the SDK from here.
If you have the folder but still have the problem, go to your Environment Variable, add that folder to the end of PATH variable and restart the PC.
I have been pulling my hair for the past couple days trying to figure out how set up a CI/CD process just to build a simple WPF solution and create the MSI setup file ("artifact") using Azure DevOps Pipelines. I have tried using Build VS Installer to accomplish this. My main problem is that I don't know exactly what am I doing wrong or what steps I am missing and I can't find clear instructions on this anywhere.
Here's what I've tried:
Using the Hosted 2017 agent pool and the basic .NET Desktop Template. Problems:
Create .msi file(s) from VS Installer project(s) as last task or before publishing artifact):
2018-11-28T22:57:56.3186071Z DEBUG: Aggregated: C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.com
2018-11-28T22:57:56.3211382Z Now running (C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\devenv.com) with Arguments ("D:\a\1\s" /Build "release|any cpu" /Out "D:\a\1\b\BuildInstaller_Log_20181128225756.txt")
2018-11-28T22:58:54.0015320Z Done running DevEnv process. Success = True.
2018-11-28T22:58:54.1169279Z ##[warning]No .MSI files were found, please check your build-configuration. If this is expected, you might consider to use the default Visual Studio Build task instead of this custom Installer task.
2018-11-28T22:58:54.1434410Z ##[section]Finishing: Create .msi file(s) from VS Installer project(s).
Creating my own build agent as outlined in the documentation. I have Visual Studio Community 2017 with the VS Installer Projects extension installed on that server. I followed the steps from this related answer. Results:
2018-11-29T17:46:03.9813075Z DEBUG: Aggregated: System.Object[]\devenv.com
2018-11-29T17:46:04.4346060Z ##[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object[]
2018-11-29T17:46:04.4716416Z ##[section]Finishing: Create .msi file(s) from VS Installer project(s).
I also tried DevEnv Build from the market place instead of the DutchWorkz one and still couldn't get an .msi file. Can someone please show me some clear steps on how to achieve this simple goal?
I was able to figure out why I was getting the specific error message below and wanted to share in case it helps anyone out in the future.
DEBUG:
Aggregated: System.Object[]\devenv.com
[error]Cannot retrieve the dynamic parameters for the cmdlet. The specified wildcard character pattern is not valid: System.Object[]
The issue was that I had two versions (Professional and Enterprise) of Visual Studio 2017 installed on my private build server. Once I removed one of them, everything worked great. Not sure if there's a way to get it working with both installed, but I didn't need both.
Microsoft Visual Studio Installer Projects extension is present in windows-latest runner. Find more here
In short, use an agent with windows-latest vmimage and build via devenv.exe instead of MSBuild.
I am using Visual Studio 2013/ISLE to create a C# program with a .msi install image. When I run install from VS the program is installed in the expected location, e.g. c:/Program Files (x86)/...
I'm sure that this is something simple but I can't figure it out. A pointers would be greatly appreciated.
When you run a 32-bit installer in x 64-bit system Windows will always redirect your installer writing to c:\Program Files to c:\program files (x86). If you want to install to the non-x86 folder you will need to provide a 64-bit installer for your application.
This blog post explains why Windows does this.
It looks like InstallShield LE will allow you to write to the correct folder when your project is set to AnyCPU, but for more advanced scenario's you'll need to use the Pro version or the free Wix installer.
I assume the question is why the installation MSI fails when you run it outside of Visual Studio, but works when VS launches it?
If yes, you should first check if your ISLE project is creating an MSI or an EXE bootstrapper (that also contains the MSI). If an EXE is created this is what you should launch manually, not the MSI. In theory, a bootstrapper can act like an initialization support for the MSI and specify default values for certain properties, like an installation folder, etc...
I say in theory because I am not very familiar with ISLE, I work with other setup authoring tools, thus cannot say for sure if this stands for ISE projects too.
I have inherited this c# solution that includes an ix installer project (a bunch of .wxs files and some c# files). The uninstaller is generating an error message.
I haven't a clue what this installer project is. What are the .wxs files for? I can guess (and have successfully been able to fix some issues with the installer. I have figured out how the custom actions are set up and called etc.
But the bug in question would be so much easier to debug if I could step through it in the debugger - how do I do that?
Generally: How do I hook up the Visual Studio 2008 debugger with the installer project ("Set as Startup Project" is not an option in the Solution Explorer, tried that).?
Specifically: How do I debug the uninstaller? The way I see it, the uninstaller will have to use a dll not residing in the project folder (where?) and thus not really known to Visual Studio at all...
Maybe this article on MSDN will help.
I haven't done it recently but I think that if you add anywhere in the code Debugger.Break() statement, you will get a prompt during the install to debug the process and then you can step through it.
One of the pages that look promising is the WixWiki.
I found this on the wikipedia page for WiX.