Unable to install Microsoft.CodeAnalysis NuGet package

[mrward]

Unable to install the new Roslyn NuGet package into SharpDevelop.

To reproduce

Create a .NET 4.5 C# console project.
Select IncludePrerelease checkbox.
Search for "id:Microsoft.CodeAnalysis".
Click the Add button.

Expected result

Microsoft.CodeAnalysis and several other NuGet packages are installed and assembly references are added.

Actual result

Nothing happens.

Looking at the code the Microsoft.CodeAnalysis has no assembly references so it is treated as a solution package and none of its dependencies are installed. The code should probably check dependencies. However it might be worth looking at the NuGet source code to see how this is handled.

Would be good to have unit tests for the new solution level packages and this bug.

[mrward]

There packages are downloaded into the packages folder but no assembly references are added to the project and the packages.config file is also not updated.

If you look in the Output window you will see that nothing happens after the dependencies are resolved. There are no error messages.

If you install the Microsoft.CodeAnalysis package with Visual Studio you see that the packages.config is updated:

<?xml version="1.0" encoding="utf-8"?>
<packages>
  <package id="Microsoft.Bcl.Immutable" version="1.1.20-beta" targetFramework="net45" />
  <package id="Microsoft.Bcl.Metadata" version="1.0.9-alpha" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis" version="0.6.4033103-beta" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis.Common" version="0.6.4033103-beta" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis.CSharp" version="0.6.4033103-beta" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis.CSharp.Workspaces" version="0.6.4033103-beta" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis.VisualBasic" version="0.6.4033103-beta" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis.VisualBasic.Workspaces" version="0.6.4033103-beta" targetFramework="net45" />
  <package id="Microsoft.CodeAnalysis.Workspaces.Common" version="0.6.4033103-beta" targetFramework="net45" />
</packages>

The project has several references added.

This does not seem to happen with SharpDevelop 5.

You can change the .NET platform when you create the project or from the Project Options, Compiling tab, Target Framework.

I believe the problem is that the Microsoft.CodeAnalysis package is being treated as a solution level package when it can actually be installed into a project.

[ddur]

I can install references of dependent packages from (solution) install tab.
Looks like dependent (project) packages are not installed into project when depend on solution package

[mrward]

I could be wrong but Microsoft.CodeAnalysis does not seem to be a solution package. Visual Studio puts the package id into the packages.config so that it seems to be not treated as a solution package here.

Looking at the NuGet source code a package is not a solution level package if it depends on other packages:

        /// <summary>
        /// Check to see if this package applies to a project based on 2 criteria:
        /// 1. The package has project content (i.e. content that can be applied to a project lib or content files)
        /// 2. The package is referenced by any other project
        /// 3. The package has at least one dependecy
        /// 
        /// This logic will probably fail in one edge case. If there is a meta package that applies to a project
        /// that ended up not being installed in any of the projects and it only exists at solution level.
        /// If this happens, then we think that the following operation applies to the solution instead of showing an error.
        /// To solve that edge case we'd have to walk the graph to find out what the package applies to.
        /// 
        /// Technically, the third condition is not totally accurate because a solution-level package can depend on another 
        /// solution-level package. However, doing that check here is expensive and we haven't seen such a package. 
        /// This condition here is more geared towards guarding against metadata packages, i.e. we shouldn't treat metadata packages 
        /// as solution-level ones.
        /// </summary>
        public bool IsProjectLevel(IPackage package)
        {
            return package.HasProjectContent() ||
                 package.DependencySets.SelectMany(p => p.Dependencies).Any() ||
                _sharedRepository.IsReferenced(package.Id, package.Version);
        }

[ddur]

Will you do it or I can try?

[ddur]

There is extension in IPackageExtension.cs that maybe can help

     public static bool IsProjectPackage(this IPackage package)
        {
            return package.HasProjectContent();
        }