-
Notifications
You must be signed in to change notification settings - Fork 252
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
Dependency conflict when project.json reference csproj #2865
Comments
This works fine in VS or through msbuild but not with dotnet restore which is as designed as of now. @sayedihashimi dotnet restore works only with xproj in current design and will need framework changes to support csproj. |
@jainaashish If I understand you correctly, then it is literally impossible to build a combined project.json + csproj solution right now with msbuild and that's as designed? If you read the linked issues, you'll see people are trying to build simple sites that reference a csproj project on a build server and the build is breaking, while working in VS. |
This is being fixed by the move of .NET Core projects to use project files, instead of Project.Json. |
@rrelyea Trying this VS2017, after a conversion of a xproj to a csproj, there is no packages.config files. You can repro this by creating a new ASP.net Framework web app. Then run what Azure would run:
You'll get
Then, it won't compile... NuGet is 3.5 |
@jsgoupil if you modify what Azure runs to run |
I spent so much time on this... just added 2 more hours and I didn't succeed much. dotnet restore works but it doesn't create the /packages like VS2017 does IF you have a Class Library. (Is it needed though?) My project GUID is 7B770C35-F561-4221-8A08-E6646CB96DCE. I have noticed that the new Class Library in 2017 have 4DAECC67-F322-4E30-8B4A-A7F6D588ABD5. There are too many variables that I cannot try them all. It's just not working. When can I expect this to work on Azure out of the box. |
Port of https://github.com/dotnet/cli/issues/3205
The text was updated successfully, but these errors were encountered: