Got 'Task could not find "AxImp.exe"' error on both OSX and Ubuntu
See original GitHub issueEnvironment data
dotnet --info
output:
.NET Command Line Tools (2.0.0)
Product Information: Version: 2.0.0 Commit SHA-1 hash: cdcd1928c9
Runtime Environment: OS Name: Mac OS X OS Version: 10.12 OS Platform: Darwin RID: osx.10.12-x64 Base Path: /usr/local/share/dotnet/sdk/2.0.0/
Microsoft .NET Core Shared Framework Host
Version : 2.0.0 Build : e8b8861ac7faf042c87a5c2f9f2d04c98b69f28d
VS Code version: 1.14.2 (1.14.2) C# Extension version: 1.12.1
Steps to reproduce
Hi all! I’m new to c#, and I’m trying to build and run an existing .NET project
First I tried to use vscode with c# extension on Linux, I’ve installed both mono and dotnet, and both command can be execute from command line, but in vscode, I get these errors and no Intelli sense in the editor:
[fail]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
Task could not find "AxImp.exe" using the SdkToolsPath "/" or the registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\NETFXSDK\4.7\WinSDK-NetFx40Tools-x86". Make sure the SdkToolsPath is set and the tool exists in the correct processor specific location under the SdkToolsPath and that the Microsoft Windows SDK is installed
It’s really confusing because I can’t locate the file AxImp.exe anywhere in my computer. Looks like the extension is treating me like a an Windows machine or something ?
After that I switched to OSX and got the same issue, which is really strange to me.
FIY: I can build the .NET project on Ubuntu using MonoDevelop( but I really want to develop it with VSCode! ), so I guess I’ve already installed all requirements in my Ubuntu machine.
Thanks for help and sorry for my English 😃
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:12 (4 by maintainers)
Top GitHub Comments
@DustinCampbell : Thank you for your response! I had Mono and dotnetcore-sdk installed, but was missing MSBuild. Thanks again for your quick response and assistance.
Will close this out as a wontfix for now, since the scenario of WinForms on Mono is going to be considered out of scope.