New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot Publish neon project. Build fails, neon.dll missing. #90

Closed
Agouri opened this Issue Jan 13, 2018 · 5 comments

Comments

5 participants
@Agouri

Agouri commented Jan 13, 2018

As the title says, a virgin, fresh copy of this repo fails to build and Publish. Nothing changed in it.

The error:

1>------ Build started: Project: neon, Configuration: Release Any CPU ------
1>neon -> C:\Users\Dimitris\Downloads\neo_compiler_latest\neo-compiler-master\neon\bin\Release\netcoreapp1.0\neon.dll
2>------ Publish started: Project: neon, Configuration: Release Any CPU ------
2>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin\Roslyn\csc.exe /noconfig /unsafe+ /checked- /nowarn:1701,1702,1705,2008 /nostdlib+ /platform:anycpu /errorreport:prompt /* About a million other /settings here */
2>Could not copy the file "obj\Release\netcoreapp1.0\win10-x64\neon.dll" because it was not found.
========== Build: 1 succeeded, 0 failed, 0 up-to-date, 0 skipped ==========
========== Publish: 0 succeeded, 1 failed, 0 skipped ==========

I've found neon.dll under \neo-compiler-master\neon\bin\Release\netcoreapp1.0\, but it's looking for it in obj\Release\netcoreapp1.0\win10-x64\. Maybe an error in the manifest?

@tvance929

This comment has been minimized.

tvance929 commented Jan 14, 2018

Mine builds fine if I build out each project one at a time, but will not Publish or at least I get an error. (However I do have neon.exe here: bin\Release\netcoreapp1.0\win10-x64)

I see this in the output - although these are just warnings:
image

My tmp file says:

1/14/2018 11:05:00 AM
System.AggregateException: One or more errors occurred. ---> System.Exception: Publishing failed.
--- End of inner exception stack trace ---
at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)
at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)
at Microsoft.VisualStudio.ApplicationCapabilities.Publish.Model.DefaultPublishSteps.<>c__DisplayClass22_0.b__1()
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.ApplicationCapabilities.Publish.Model.DefaultPublishSteps.d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.ApplicationCapabilities.Publish.ViewModel.ProfileSelectorViewModel.d__108.MoveNext()
---> (Inner Exception #0) System.Exception: Publishing failed.<---

===================

@Agouri

This comment has been minimized.

Agouri commented Jan 14, 2018

@tvance929 Same warnings here too, but I think these have nothing to do with failure to publish. They're just warnings.

@tvance929

This comment has been minimized.

tvance929 commented Jan 14, 2018

OK so the docs tell you to just go ahead and manually copy that dll file to the "neon\obj\Release\netcoreapp1.0\win10-x64" folder ...did that and now I published fine. Thanks @Agouri for pointing out that it was missing the neon.dll file.

From : http://docs.neo.org/en-us/sc/getting-started-csharp.html
image

@NeoParticle

This comment has been minimized.

NeoParticle commented Feb 27, 2018

use command prompt and navigate to neon folder.
type "dotnet publish -c release -r win10-x64" and press enter..
:)
The issue seems to be is in Roslyn compiler.. So do it manually.

@jephambl

This comment has been minimized.

jephambl commented Mar 2, 2018

what worked for me :

  1. use command prompt and navigate to neon folder.
    type "dotnet publish -c release -r win10-x64" and press enter
  2. right publish in VS
    et voilà !
    neo compiler publish

@erikzhang erikzhang closed this Oct 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment