Difficulty compiling; apparent package update and namespace issues #20
Comments
|
I tried to compile without updating, but then it complained about namespaces, so I thought I'd update. |
eglassman
changed the title
|
Updating packages one by one, in reverse order, to see if that helps. |
|
@gustavoasoares, I have brought the Windows VM back up, pulled the newest commit, and got the following error report, which is similar but distinct to what I was getting on my Mac:
From the web, about the first error in this report, I got one of the most helpful things I've gotten so far: |
|
Can you try:
|
|
Weirdly, that appears to be a NOP: However, I was able to go into the Nuget package manager and trigger 11 updates which it's now trying to install. As a result, I get the same error as I got on the Mac: |
|
We're not the only ones with this annoying error! NuGet/Home#1325 All seems to be related to .NET standard junk: https://blogs.msdn.microsoft.com/dotnet/2016/09/26/introducing-net-standard/ |
|
Currently trying to install updates on Windows VM installation of VS 2017, then will look into this Create-New-NuGet-Package thing to get around the .NET issue. |
|
Current build error for Refazer.WebAPI project on VS Community 2017 for Mac: and for Refazer.Experiments: |
|
Uninstalled all codeanalysis packages. (There were multiple listed in the project, and some depended on each other; I deleted all of them.) Tried to reinstall the Microsoft.CodeAnalysis nuget package and received the same error as before: |
|
Another relevant link from googling the error message: dotnet/roslyn#18954 Roslyn appears to be the name of the project on github that includes the nuget package for Microsoft's CodeAnalysis. Highlights of that conversation: Response from Roslyn author/maintainer? (presumably at MS): The maintainer in the conversation I quoted above does acknowledge that this entire issue may be a bug on their end. Awesome! |
|
It was unclear how to force our solution to use .NET Framework 4.6. I manually changed all instances of 4.5.2 to 4.6 in my local copy of the code, uninstalled all packages that include or depend on CodeAnalysis, cleaning, rebuilding, etc. but it still tried to use 4.5.2 as a target. Then I found this option and updated it to 4.6 for every project in the solution: This step, above, worked!!!! I am a genius!!! haha, jk @gustavoasoares |
|
Okay, still cannot build without errors, but I feel we have made progress: More screenshots of errors:
|
|
In parallel, I have updated the targets (using the GUI) for each of 4 projects, and now I'm getting this error when I build one of the projects:
|
|
I am trying an "Incredibuild" just in case that helps haha |
|
Thanks @eglassman! It seems there is a problem because VS 2017 uses Nuget 4.x, which does not use package.config to configure the dependences. On windows, VS 2017, can you try to download the latest code from the master branch, and then build the solution? Please let me know if this works. |
|
Updating my Windows VM and will follow your instructions ASAP. |
|
|
|
@gustavoasoares still buggy :/ |
|
Whoops, I forgot to manually restore the packages. Will do that now!
…On Sun, Jun 25, 2017, 6:42 PM Gustavo Soares ***@***.***> wrote:
Thanks @eglassman <https://github.com/eglassman>! It seems there is a
problem because VS 2017 uses Nuget 4.x, which does not use package.config
to configure the dependences. On windows, VS 2017, can you try to download
the latest code from the master branch, and then build the solution?
I still need to refactor Refazer.Web from nuget 2.x to nuget 4.x. So you
need to manually restore the packages for this project. You can download
nuget.exe (https://dist.nuget.org/index.html), go to refazer/package
folder, and run:
path-to-nuget.exe\nuget.exe install ..\Refazer.Web\packages.config
Please let me know if this works.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#20 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACNnQviXVUHtpC41hqD2ZUjvYd0jOuU9ks5sHwxmgaJpZM4OBogw>
.
|
|
Ran command, got the following: @gustavoasoares I used the VS2017 GUI for uninstalling packages for all the projects in the solution, but I still get the same error. :/ |
|
There's relevant information here for a nuget package concole command-line way to uninstall: https://docs.microsoft.com/en-us/nuget/consume-packages/reinstalling-and-updating-packages However, I don't see how this should be any different from the GUI. |
|
Clean clone of repo, built Solution straight away, got the following error about packages: Ran Ran that image, annotated: |
|
Ok. We are almost there. You should not have run this command:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After trying to update my packages, I got the following error:
@gustavoasoares, what .NETFramework version do you have?
The text was updated successfully, but these errors were encountered: