http://docs.asp.net/en/latest/tutorials/your-first-mac-aspnet.html
Installed Node
Installed Yo
yo aspent
pick the web application
dnu update
dun build failed with spectacular 2400 odd errors
open the vsCode as we can issue a command on the top that did not work failed and complained omni sharp is not working.
dun went with beta version 1.0.0.4
some where i saw depends on mono downloaded mono installed it.
re-open VSCode and still fails to run with the following error message
error from the vscode
[INFO] Starting OmniSharp at '/Users/bvn/TestApplication'...
[INFO] Started OmniSharp from '/Users/bvn/Downloads/Visual Studio
Code.app/Contents/Resources/app/extensions/jrieken.vscode-omnisharp/bin/omnisharp'
with process id 2775...
[INFORMATION:OmniSharp.Startup] Omnisharp server running using stdio
at location '/Users/bvn/TestApplication' on host 2765.
[INFORMATION:OmniSharp.Dnx.DnxPaths] Using runtime
'/Users/bvn/.dnx/runtimes/dnx-mono.1.0.0-rc1-update1'.
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] Scanning
'/Users/bvn/TestApplication' for DNX projects
[INFORMATION:OmniSharp.Dnx.DnxProjectSystem] Found project
'/Users/bvn/TestApplication/project.json'.
[INFORMATION:OmniSharp.Dnx.DesignTimeHostManager] Listening on port
57325
[INFORMATION:OmniSharp.Dnx.DesignTimeHostManager] Process ID 2784
[ERROR:OmniSharp.Dnx.DesignTimeHostManager] Failed to launch
DesignTimeHost in a timely fashion.
[ERROR] Error: Failed to start OmniSharp
[INFORMATION:OmniSharp.Dnx.DesignTimeHostManager] Client accepted
127.0.0.1:57325
Here is how I manually installed OmniSharp into VS Code. I used the steps in this link to help point me in the right direction. After some tinkering, I got everything working in both OmniSharp within VS Code and the dotnet core debugger integration. The link above implicitly suggests putting files in the .bin\omnisharp\ folder (note the . prefixing bin) but, that didn't work... it worked when I put files in the bin\omnisharp\ folder.
I'm running Windows 10 64bit and .Net Core SDK/CLI v1.0.4 with VSCode v1.14.2. Here are the steps:
Install OmniSharp in VSCode and then close VSCode
If it does not already exist, create bin\omnisharp and .debugger folders under %userprofile%\.vscode\extensions\ms-vscode.csharp-1.11.0\
In the runtimeDependencies section of this packages.json, download the zip files for OmniSharp (.NET 4.6 / x64) and for .NET Core Debugger (Windows / x64)
Unzip omnisharp-win-x64-<version>.zip into %userprofile%\.vscode\extensions\ms-vscode.csharp-1.11.0\bin\omnisharp\
Unzip coreclr-debug-win7-x64.zip into %userprofile%\.vscode\extensions\ms-vscode.csharp-1.11.0\.debugger\
Launch VSCode and run thru a simple Hello World dotnet core example... everything should work.
I hope the info helps. :)
Related
I cannot for the life of me get F# to run in Visual Studio Code. I've had it up and running previously, but not with the most recent versions of the software.
I installed the most recent versions of .NET and VS code a month ago and again now, did full deletes and re-installs both times (including deleting user/.vscode and roaming/Code manually), but the error persists.
I am on a Windows 10 and have installed x64 versions of .NET Core 3.1 and VS Code 1.48 with the only extensions C# 1.23 and Ionide-fsharp 4.16. I have enabled Use Sdk Scripts for ionide, but otherwise run on default configuration. dotnet fsi is executed without problems in the command line.
Looking at the VSC extension host log:
[2020-08-15 11:24:35.431] [exthost] [error] Error: Language client is not ready yet
at LanguageClient.sendRequest (c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:7887:19)
at __exports.compilerLocation (c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:4290:19)
at fsacConfig (c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:4730:12)
at c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:4797:20
at Object.__exports.msbuild (c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:4802:10)
at activate (c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:19152:91)
at c:\Users\Bruger\.vscode\extensions\ionide.ionide-fsharp-4.16.0\fsharp.js:25116:90
which I believe is caused by this problem seen in the VSC F# log:
[Error - 11.24.35] Starting client failed
Launching server using command Invalid macro definition. failed.
I'm stuck here as I don't know what macro definition this refers to or how to get more information about the failure.
I just found the cause and solution for the problem. It had nothing to do with Ionide or Visual Studio Code. Instead my cmd was acting up due to misconfiguration.
For a while the message "Invalid macro definition" has been output as the first thing when I open cmd, but I didn't see the connection to the problem above. Turns out that VS code did not like this output and that it was the AutoRun configuration for cmd that triggered this error.
Using regedit, I found that I had several AutoRun files that were no good, so I removed them from respectively Computer\HKEY_CURRENT_USER\Software\Microsoft\Command Processor and Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor and the problem was solved.
I get the following error when I am trying to build a project in Unreal, that I have included some lightning. "Lighting Build Failed. Swarm failed to Kick off. Compile Unreal Lightmass".
I have build Unreal Engine 4.24.1 from source on Linux with the setup instructions from the documentations.
Any ideas how to proceed. How would I go and compile Unreal Lightmass for the Engine?
After some sparse search here and there, I was able to solve this.
To compile the UnrealLightmass there is a build shell script in the directory
UnrealEngine_Repo_dir/Engine/Build/BatchFiles/Linux
You need to run the ./Build.sh with the following input
./UnrealEngine_Repo_dir/Engine/Build/BatchFiles/Linux/Build.sh UnrealLightmass Linux Development -verbose
This should start compilation and build the UnrealLightmass.
This probably is the way to build the remaining programs that the Unreal Engine would complain that you haven't build.
Any program that is under the directory
/UnrealEngine_Repo_dir/Engine/Source/Programs
can be build with the above command. One example would be the ShaderCompileWorker.
Hope this helps.
If you did the full source build setup process, Lightmass should have compiled as well. Here is a probably-foolproof solution:
Run Setup.sh
Run GenerateProjectFiles.sh
Once the Visual Studio .sln is finished generating, open that.
Wait for the option to appear, then (Toolbar) Build->Build Solution
The UEBuildTool should then compile everything in the project, including Lightmass.
After installing the latest Atlassian JIRA SDK on Windows, I try to run the first tutorial but I'm getting a BUILD FAILURE.
This all works fine on Mac OS High Sierra (of course), but not Windows.
I am using the following environment:
Windows Server 2008 R2
Java 1.8.192
JAVA_HOME=C:\Java\jdk1.8.0_152
I am trying to create the example plugin.
https://developer.atlassian.com/jiradev/getting-started/getting-started-with-plugins2
I am following the tutorial's instructions, and not modifying anything. I
downloaded sdk-installer-6.2.15.exe and installed.
created a directory, C:\JIRA and cd'd to it.
ran the command atlas-create-jira-plugin
filled in prompts following the tutorial.
ran atlas-run
I get the error:
BUILD FAILURE
Failed to execute goal com.atlassian.maven.plugins:maven-amps-dispatcher-plugin:6.2.11:run (default-cli) on project myPlugin: Unable to execute mojo: archive is not a ZIP archive
I am trying to run a .NET Core version 1.1 application from inside VS Code version 1.8.1. When I push the F5 button, the console appears at the bottom of the screen. After enabling tracing, I get this output:
Reading fx resolver directory=[C:\Program Files\dotnet\host\fxr]
Considering fxr version=[.]... Considering fxr version=[..]...
Considering fxr version=[1.1.0]... Detected latest fxr
version=[C:\Program Files\dotnet\host\fxr\1.1.0]... Resolved fxr
[C:\Program Files\dotnet\host\fxr\1.1.0\hostfxr.dll]... Loaded library
from C:\Program Files\dotnet\host\fxr\1.1.0\hostfxr.dll Tracing
enabled
--- Invoked hostfxr [commit hash: 928f77c4bc3f49d892459992fb6e1d5542cb5e86] main Own DLL
path=[C:\Program Files\dotnet\dotnet.dll] Checking if CoreCLR path
exists=[C:\Program Files\dotnet\coreclr.dll] Detecting mode... CoreCLR
present in own dir [C:\Program Files\dotnet] and checking if
[dotnet.deps.json] file present=[0]
--- Executing in split/FX mode... Detected a non-standalone application, expecting app.dll to execute. Application 'build' is not
a managed executable.
Also, a bar appears at the top of the screen that says:
The preLaunchTask 'build' terminated with exit code 2147516564.
When I click the "show problems" option, a blank problems tab appears that contains the message:
No problems have been detected in the workspace so far.
Why is VS Code refusing the build the project, and why are there no problem messages? I am only posting this on SO, because Google was not helpful, and because the VS Code GitHub page recommends asking questions here first.
UPDATE
This problem was caused by me having put coreclr.dll in C:\Program Files\dotnet. I did this, because of a different problem related to building the app. I thought that, since the output mentions it is looking in this directory, it might be helpful to put this file here. It turns out that this was a very bad idea, as it just complicated the problem! LOL!
You can get this error if you have problems in:
packages - please check if all packages are ok and restored successfully
core version - check that core installed with correct version
.net tools - please check if version of .net tools correct.
Can you try visual studio?
I am running VS2010 Ultimate, I used to have VS Web Dev 2010 Express with Nuget before: I uninstalled it before installing Ultimate.
In admin mode I uninstalled Nuget 1.5 from vs, restarted vs in admin mode, installed 1.6, and then restarted vs. Nuget worked for several days.
The next day, the package manager wont come up - it doesnt give me an error, it just wont load. If I try to uninstall it, the uninstall button is greyed out (which I assume means that the addin is in use). If I restart vs, then I can uninstall.
I have tried uninstalling Nuget and reinstalling it several times (no error messages generated)
Trying to load Package Manager Console and the Package Manager Settings, dont launch anything.
Is there a way to install version 1.5? I've looked for a link but cannot find one.
Is there a log file I can check to see what is wrong?
This has been an extremely frustrating issue for me.
Update:
I used devenv /log, tried to open the package console.
Here's part of the log file:
225 Leaving function LoadDTETypeLib VisualStudio 2011/12/30 21:54:45.181
226 ERROR SetSite failed for package [NuGet.Tools.NuGetPackage, NuGet.Tools, Version=1.6.21215.9133, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a] {5FCC8577-4FEB-4D04-AD72-D6C629B083CC} 80131509 VisualStudio 2011/12/30 21:54:45.196
227 ERROR End package load [NuGet.Tools.NuGetPackage, NuGet.Tools, Version=1.6.21215.9133, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a] {5FCC8577-4FEB-4D04-AD72-D6C629B083CC} 80131509 VisualStudio 2011/12/30 21:54:45.227
228 Warning Package failed to load; error message suppressed by skip flag {5FCC8577-4FEB-4D04-AD72-D6C629B083CC} VisualStudio 2011/12/30 21:54:49.486
229 Entering function CVsPackageInfo::HrInstantiatePackage
Thanks!
Finally got it working: had to delete c:\User Data\\AppData\Roaming\NuGet\NuGet.Config (which was empty) and now it can load.
I had the same problem, nuget worked yesterday but not today with "SetSite failed for package [NuGet.Tools.NuGetPackage" in the VS log.
After a lot of trying and failing I found this page, and then the discussion at http://nuget.codeplex.com/discussions/284604
I followed the advice from bsparkinson there :
Unistalled Nuget.
Searched for nuget in %appdata% and deleted everything
Reinstalled Nuget.
And now it works.
You mentioned:
If I try to uninstall it, the uninstall button is greyed out (which I
assume means that the addin is in use).
Is it greyed out even when you run VS as an admin? The button should only be greyed out if you're not running as admin.
The other thing you should do is try running the following command. You'll need to use the devenv command prompt.
vsixinstaller.exe /uninstall:NuPackToolsVsix.Microsoft.67e54e40-0ae3-42c5-a949-fddf5739e7a5
That should uninstall the NuGet VSIX. After doing that, the following directory should be gone or empty: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\\