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

Update command might be a bit more verbose if i ask it to be so... #2418

Closed
Piet-van-Bruggen opened this Issue Mar 30, 2016 · 2 comments

Comments

Projects
None yet
5 participants
@Piet-van-Bruggen

Piet-van-Bruggen commented Mar 30, 2016

A simple problem has cost me quite some headaches.. I used the NuGet commandline update command and supplied a solution to it... for some reason it seemed to work, but it didn't.

If found out that there was a message like:

Scanning for projects...
Found N projects with a packages.config file.

And I found out that my solution had N+1 projects so that was my starting point... But what I tried to specify (Verbose, Verbosity) nothing showing me why it didn't update that one other project...

So I fetched the sources and searched a bit, then found this piece of code on line 162 of the file src\NuGet.Clients\NuGet.CommandLine\Commands\UpdateCommand.cs

    private MSBuildProjectSystem GetProject(string path, INuGetProjectContext projectContext)
    {
        try
        {
            return GetMSBuildProject(path, projectContext);
        }
        catch (CommandLineException)
        {

        }

        return null;
    }

The root cause of my problem is that for some unknown reason there was a second csproj file in the path of the project that was skipped. I'm not going to argue whether or not this should have been supported (the second project file was not in my solution), but at least a writeline of the exception to the console (maybe even only when in Verbose) would be nice ;)

@yishaigalatzer

This comment has been minimized.

Show comment
Hide comment
@yishaigalatzer

yishaigalatzer Mar 30, 2016

Yes, we completely agree with you.

yishaigalatzer commented Mar 30, 2016

Yes, we completely agree with you.

@joelverhagen

This comment has been minimized.

Show comment
Hide comment
@joelverhagen
Member

joelverhagen commented May 18, 2016

@zhili1208 zhili1208 modified the milestones: 3.5 Beta2, 3.6 Beta Jun 22, 2016

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