"ssexp" command is not working to start visual sourcesafe explorer - command-line

If anyone knows how to start visual sourcesafe explorer, please write steps. I followed the steps mentioned in MSDN but it is giving error.
'ssexp' is not recognized as an internal or external command, operable program or batch file.

Did you successfully install Source Safe 2005? See:
How to: Install Visual SourceSafe on a Client Machine
How to: Install Visual SourceSafe on the Server Machine
Did you use the CD command to navigate to the directory for the Visual SourceSafe installation? That error message usually means you are not in the correct directory.

Related

Microsoft Visual Studio Developer command prompt

After installing Microsoft Visual Studio community 2019 and choosing game development on installer, as well as microsoft visual studio code, i open the developer command prompt and there's an error already there. 'C:\Program' is not recognized as an internal or external command, operable program or batch file. Then typing cl, i get the same error.

Unable to find the TF executable while adding tfs to VSCode

I am adding TFS to Visual Studio Code IDE(1.42.0) for that I have installed Azure Repos extension.
In VS code at File-->Preference-->Setting-->Tfvc:Location, when I am entering path C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\tf.exe.
Getting error
(team) Unable to find the TF executable. Please ensure TF is installed
and the path specified contains the filename.
How can I solve this issue?
Edit 1: After installing Azure Repos extension, I am entering above path in tfvc:Location(for both tabs User and Workspace), but after entering path nothing happens. Check below screenshot
Edit2: Now I am getting this error at right below in VS code IDE
Since you have not got any help yet. I will take a shot. Any chance there is a issue with finding the executable and casing for the extension? My local TF is capitilized. \TF.exe
Also might want to checkout the Github and readme for TFVC.
Make sure you have installed VS on your computer. With a typical installation of Visual Studio, the Windows version of the TFVC command line client (tf.exe) is available under the Program Files (x86) folder. It will typically be placed in a location similar to C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe. On the 2017 version of Visual Studio Community, it can be found in a location similar to C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\TF.exe.
I found a .vscode folder in my project
delete it, close and reopen vscode solved the problem

'code' is not recognized as an internal or external command - Microsoft Visual studio Code

I am using visual studio code for develop my react application. I just wanted to open the project in the IDE using CLI, using "code ." command. Although it was perfectly working previously, now shows an error as below.
'code' is not recognized as an internal or external command,
operable program or batch file.
Can someone help me out to solve this matter?
This sounds like an issue with your environment variables rather than a problem with VS Code itself.
When you run the code command in Windows Command Prompt (cmd), Windows searches all commands on your path for one named code, and executes that command. VS Code installs a command with this name that opens the editor, normally located here on Windows:
C:\Program Files\Microsoft VS Code\bin
It may be that your path no longer contains this particular directory for some reason.
You can edit your path directly to add it:
From the Start menu, type "variables" and choose the option to "Edit environment variables for your account".
Locate the PATH entry and edit it.
Add the directory where the code command exists, e.g. C:\Program Files\Microsoft VS Code\bin.
The path editor may appear slightly different depending on what version of Windows you are running.
My case was different rather than general solution for this question. I saw that the number of solutions which says the probelm exists with the environment valriables. In the new release it provides a setup file only.
Before downloading, there are certain properties to be selected.When I just redownloaded the set up and run it , it starts working perfectly.

Nuget CLI not available even with VS 2017 RC3

The Nuget Distribution pages states:
NuGet 4.x is included in the Visual Studio 2017 installation. Latest
NuGet releases are delivered as part of Visual Studio updates.
Batteries are included!
It seems those batteries are flat. In both Package Manager Console and extenal PS windows, when I type nuget, I get the error:
The term 'nuget' is not recognized as the name of a cmdlet, function,
script file, or operable program.
What do I have to do to fix this? If it's installed with VS 2017, surely that install should add it to the PATH variable?
I don't want to use the VS Command Console, even if it is still with 2017, as I have retired all my usage of that relic to PowerShell consoles.
All I had to do was add the location of nuget.exe to the PATH environment variable for my user and all users, The latter is up to you, but I always run VS as Administrator.
Sages of yore used to always advise against doing this, but MS in all their divine wisdom has made life as a web developer using VS so difficult under a non-admin account, I see nary a mention of said advice, even since around VD 2010 even.
You'd think that with Nuget being installed as part of Visual Studio, the least they could do is add amend that bloody variable as part of the VS installation.

File Not found exception - speechclient.dll NuGet Package

I have a project using the SpeechClient.dll from NuGet. The program runs fine on the development machine. So I have a Windows Setup Project that creates the installer. I run the installer and all the files show up including the SpeechClient.dll, but as soon as the program makes the first call to the Speechclient.dll, I get a
file not found
exception. This is the output from the event viewer.
Does anyone have any troubleshooting ideas? Thanks.
Seems now that I have installed visual studio on the machine that it is working. I wonder what visual studio installs? I was also trying to use Fusion Log Viewer to see what the problem was.
I had this problem as well. Installing the Visual Studio C++ Redistributable 2017 x64 cleared it up.