I have just started using ConEmu. I have tried different shells like the default windows cmd and the Powershell which worked fine. When i tried to add visual studio shell, it didn't work.
I tried "New console dialog". In that i gave this as the path for shell
C:\Program Files (x86)\Microsoft Visual Studio 11.0\VC\vcvarsall.bat
That gave me this error
Root process was alive less than 10 seconds, Press Esc or Enter
After searching in the internet i even tried an other path as mentioned in a website C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\vcvarsall.bat. That gave me the same error again!
cmd /k "C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\Tools\vcvarsall.bat"
Related
I am trying to "compile without linking" a code meant to be used as multithreaded .dll in future. I am using VS 2019 for the same. Here is the command that I have used:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX64\x86\cl.exe" /c /MD "C:\SpiceOpus\bin\ifspec.c"
This returns the following response:
ifspec.c
c1: fatal error C1356: unable to find mspdbcore.dll
This file is however present in the following 3 locations in my system as confirmed by using dir /s mspdbcore.dll :
A)
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE
B)
C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX64\x64
C)
Directory of C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX86\x86
Thus, I would like to know how to instruct the compiler for the presence of these files and then use them. I have tried using /l option for doing this as shown :
C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional>"C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX64\x86\cl.exe" /c /MD /L "C:\SpiceOpus\bin\ifspec.c"
But it says :
cl : Command line warning D9002 : ignoring unknown option '/L'
Please feel free to correct / suggest an alternative path. Kindly consider me as layman in coding things. I am in EE with not much experience in these coding stuff. Thank You.
--------------------------- Regarding PATH-----------------
Using SET command in developer cmd prompt showed this after installation for PATH variable:
Path=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE\VC\VCPackages;C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer;C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\bin\Roslyn;C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\Tools\devinit;C:\Program Files (x86)\Windows Kits\10\bin\10.0.19041.0\x86;C:\Program Files (x86)\Windows Kits\10\bin\x86;C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\MSBuild\Current\Bin;C:\Windows\Microsoft.NET\Framework\v4.0.30319;C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\IDE;C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\Common7\Tools;
If one uses cl command in Administrator developer command prompt after this, it doesn't recognize it. However, if one uses the following code:
"C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX86\x86\cl.exe"
This evokes the following response:
Microsoft (R) C/C++ Optimizing Compiler Version 19.20.27525 for x86
Copyright (C) Microsoft Corporation. All rights reserved.
usage: cl [ option... ] filename... [ /link linkoption... ]
I tried to use SET command to modify the PATH using
SET PATH=C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX86\x86\cl.exe;%PATH%
PATH gets modified but using cl command (in administrator developer cmd prompt of course ) again says that it's not recognized.
I have already repaired the installation for BuildTools using its installer. cl.exe works for sure or how else do you get the response given in point 2,5. Please let me know why cl doesn't work but writing the command in point 2 gives results? Secondly, the modified PATH variable gets restored to the original one after every reboot. How do I avoid this?
So in summary this is where I am stuck now: I have figured out that the following code seems to work partly :
"C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\bin\HostX86\x86\cl.exe" /I "C:\Program Files (x86)\Microsoft Visual Studio\2019\BuildTools\VC\Tools\MSVC\14.20.27508\include" /I "C:\SpiceOpus\source\include" "C:\SpiceOpus\bin\cfunc.c" /c /MD "C:\SpiceOpus\bin\cfunc.c"
But it just says it is generating code........ I can't find any object file from it.
As rightly commented by #dxiv i was wrong in cherry-picking during installation of MS Build Tools. So the suggestion given by #dxiv solves the issue and i no longer get the error mentioned in the title.
I got this error when trying to run dumpbin.exe from C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x86 with either the /HEADERS or /ALL flags on a 64 bit machine.
The fix was to cd C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64 and then dumpbin /HEADERS "c:\Program Files (x86)\PostgreSQL\10\pgAdmin 4\bin\libpq.dll" worked.
Since this was at the top of the search list for this error message, I wanted to report the fix.
using Visual Studio Installer, you'll want to:
Click "Modify" on your existing Visual Studio 2019/2022 install.
Select "Individual Components" on the next screen
In the search box, put in "2017"
Check the box labeled "MSVC v141 - VS 2017 C++ x64/x86 Spectre-mitigated libs"
click Install
After installation completes, you can re-run your cargo install or whatever gave you that error message and it should work. I didn't have to reboot or re-open a terminal/command prompt, it just worked once I installed.
I just upgraded from Visual Studio 2017 to Visual Studio 2019 (queue the applause). All is well and good, and I have both environments running, but...
I have a batch file that I use to start VS 2017 using the windows START and a bunch of other programs (fiddler, postman, etc). When I changed the path in the batch file to use visual studio 2019 it still loads up visual studio 2017
Neither of the Visual Studio environments are in my path and when I run the command from my command prompt
"C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe"
it loads up visual studio 2019 (yay), but when I use the START command it loads visual studio 2017.
I am on a windows 10 machine with Command Extensions turned on
START /d "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\" devenv.exe
Anyone have any idea why the START Command is loading vs2017?
Thanks
start /D "somepath" somexecutable
does not starts the executable located in somepath, it merely sets the current working directory to somepath.
What you want is this:
START /D "somepath" "somepath/somexecutable"
which in your case expands to
START /d "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\" "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\devenv.exe"
But even though you think devenv is not in your path, it must be somehow. To find where it is found try
where devenv
After Installing VS2017 I am unable to debug queries in SQL Server Management Studio 2012 (SSMS). I keep getting the error:
Unable to start program 'MSSQL:://YOUR_SERVER/YOUR_DATABASE/sys/=0'
A Visual Studio DLL, coloader80.dll, is not correctly installed.
Please repair you Visual Studio installation via 'Add or Remove
Programs' in Control Panel.
If the problem persis, you can manually register coloader80.dll from
the command prompt with 'regsvr32 "%CommonProgramFiles%\Microsoft
Shared\VS7Debug\coloader80.dll'
From: Developer Community.
To fix this issue, you can either:
Open a command prompt with administrator privileges and execute the following command:
reg add HKEY_CLASSES_ROOT\TypeLib{6A1A7D39-8449-4287-8EF0-CE256582C940}\8.0\0\win32 /t REG_SZ /d "C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\coloader80.tlb"
Alternatively you can execute:
regsvr32 "C:\Program Files (x86)\Common Files\Microsoft Shared\VS7Debug\coloader80.dll"
The correct registration will be included in future versions of Visual Studio.
I currently have a project back up on TFS. What I would like is to recover the files on the server. I tried with this command:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe" get $/Regie/Dev /recursive %userprofile%\documents\TFS
But the problem is that its copy / update in my file of my local project ... What I would like is to retrieve the project on the server to be able to copy it in any folder.
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe"
Will give you the help you need. You probably want something like this:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\TF.exe" get $/Regie/Dev /version:T /recursive %userprofile%\documents\TFS
You may also want to use /remap. See https://blogs.msdn.microsoft.com/phkelley/2012/05/18/tf-get-remap/
I recently got this error in every SSIS package (using Visual Studio 2012), when I want to open a OLE DB source component:
===================================
Method not found: 'Void Microsoft.DataTransformationServices.DataFlowUI.DataFlowConnectionPage.set_DataPreviewTimeout(Int32)'. (Microsoft Visual Studio)
------------------------------
Program Location:
at Microsoft.DataTransformationServices.DataFlowUI.OleDbSourceUI.SetConnectionPageDescriptions(DataFlowConnectionPage connectionPage)
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowAdapterUI.AddCommonConnectionPage(DataFlowComponentForm form, String helpKeyword)
at Microsoft.DataTransformationServices.DataFlowUI.OleDbSourceUI.AddPagesToForm(DataFlowComponentForm form)
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowComponentUI.EditImpl(IWin32Window parentControl)
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowComponentUI.Edit(IWin32Window parentWindow, Variables variables, Connections connections)
It worked fine last week and I don't think I changed anything since then. Any suggestions?
I ran into this same issue on a computer with Visual Studio 2010 (although I'm sure VS2012 will have the same resolution). I installed Visual Studio 2015 and then started receiving this error when I tried to open an ADO NET source or an OLD DB Source in VS2010. I found that my DatatransformationServices files in the folder C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies had become corrupt. I copied all Microsoft.DatatransformationServices files from a computer where VS2010 was working to my local computer, folder C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies.
You can use a command like the following from cmd to do so:
copy /Y "\\\GoodComputerName\C$\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.*.dll" "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\"
I then added the assemblies to my cache using the following commands in cmd (just change the directory with gacutil to your newest version in the folder C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin and change the folder for Visual Studio to the folder for the version in which you are receiving the error):
cd "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DatatransformationServices.DataFlowUI.dll"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.Design.DLL"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.DTSExecUI.Controls.dll"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.Interfaces.dll"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.VsIntegration.DLL"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.Wizards.DLL"
I just fixed the same problem with CCleaner free version by fixing broken registry entries.
For me, the problem occurred in SQL Server Data Tools 2012 which uses Visual Studio 2010 after installing multiple versions of SSDT including the 2015 Preview.
Opening any OLEDB source component raised the missing DLL error for C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DatatransformationServices.DataFlowUI.dll
The solvusoft.com site linked by GoldBishop provided useful information about the problem but recommends using their dubious product to fix it. Please read this thread on the Norton community site regarding Solvusoft and how it uses RegCleanPro.
Before using a tool like CCleaner, please research it. See who has rated it as a good product. While using it, check that it has backed up your registry entries (it does).
Quick search for this topic, lead me to another site: http://www.solvusoft.com/en/files/missing-not-found-error/dll/windows/microsoft/msdn-disc-2729/microsoft-datatransformationservices-dataflowui-dll/
- This basically states the DLL/Registry is missing/corrupt
After reviewing the MSDN documentation, I assume this is from a Drag and Drop implementation? Seems anything short of an environment DLL missing/corrupt, you may need to debug run the package to see exactly where the error is persisting.
I ran into this same issue on a computer with Visual Studio 2010 (although I'm sure VS2012 will have the same resolution). I installed Visual Studio 2015 and then started receiving this error when I tried to open an ADO NET source or an OLD DB Source in VS2010. I found that my DatatransformationServices files in the folder
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies
had become corrupt. I copied all Microsoft.DatatransformationServices files from a computer where VS2010 was working to my local computer, folder
C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies
You can use a command like the following from cmd to do so:
copy /Y "\\GoodComputerName\C$\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.*.dll" "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\"
I then added the assemblies to my cache using the following commands in cmd (just change the directory with gacutil to your newest version in the folder C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin and change the folder for Visual Studio to the folder for the version in which you are receiving the error):
cd "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DatatransformationServices.DataFlowUI.dll"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.Design.DLL"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.DTSExecUI.Controls.dll"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.Interfaces.dll"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.VsIntegration.DLL"
gacutil /if "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\PrivateAssemblies\Microsoft.DataTransformationServices.Wizards.DLL"
This resolution worked for me so I hope it works for you also :)
Works for me. Check the latest version in
C:\Program Files (x86)\Microsoft SDKs\Windows\v8.1A\bin\NETFX 4.5.1 Tools.
Had the same using SSMS 2016. This is a known issue with July 2016 release.
I didn't have the issue initially, but was messing around with SMO.
Installing 16.5.3 fixed the issue:
https://learn.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms
Sources:
https://connect.microsoft.com/SQLServer/feedback/details/2925257