Adding attributes to control nuget dependencies break the project properties tab

[jmelosegui]

Having the following solution structure.

I want to propagate the StyleCop.Analyzers package to all the project depending on ClassLibrary5. So I created the following project.json file.

{
  "supports": { },
  "dependencies": {
    "StyleCop.Analyzers": {
      "version": "1.0.0-rc2",
      "suppressParent": "none"
    }
  },
  "frameworks": {
    ".NETPortable,Version=v4.5,Profile=Profile111": { }
  }
}

After adding the StyleCop.Analyzers and specifying a json object as a value

{
  "version": "1.0.0-rc2",
  "suppressParent": "none"
}

Any project referencing the ClassLibrary5 project will have a the warning

The project 'ClassLibrary5' cannot be referenced.           

and the property windows for ClassLibrary5 project will show the following error

As soon as I modify the project.json file to.

{
  "supports": { },
  "dependencies": {
    "StyleCop.Analyzers": "1.0.0-rc2"
  },
  "frameworks": {
    ".NETPortable,Version=v4.5,Profile=Profile111": { }
  }
}

(Notice the dependency value is a string value and not a json object) everything started working again but nuget dependecies do not propagate any more and I have to explicitly add the package in every project in my solution.

Visual Studio version: 14.0.24720.00 Update 1
NuGet Package Manager version: 3.3.0

[AArnott]

I suspect this is actually a bug owned by the C#/VB project system team. @jasonmalinowski, can you confirm?

[jasonmalinowski]

I'm not sure. I cannot imagine any path where the app designer would fail to load because of an JSON parsing issue...somebody is just going to have to debug this one.

[yishaigalatzer]

Trying to find the owner of this area.

CC @emgarten @Pilchie

[Pilchie]

Is classlibrary5 (the one where the app designer fails), a portable library? cc @rchande

[yishaigalatzer]

The picture says it is

[Pilchie]

Also, is this on VS2015 RTM or Update1? I thought @rchande fixed something to do with unrecognized schema stuff in Portable as part of U1.

[Pilchie]

@jmelosegui do you have Visual Studio Update 1 installed? If not, can you try installing it and see if this still repros?

[jmelosegui]

Yes I do. Please, read the end of the original post.

[Pilchie]

Sorry for missing that. @rchande can you take a look at the project properties issue?

@jasonmalinowski can you look at "Any project referencing the ClassLibrary5 project will have a the warning: The project 'ClassLibrary5' cannot be referenced."?

@yishaigalatzer / @emgarten / @davidfowl : what is suppressParent and how does it affect the lock file?

[AArnott]

@Pilchie you can read about suppressParent here

[Pilchie]

Okay, but flowing the dependency transitively is the default, so the entry shouldn't be needed for @jmelosegui's scenario.

[AArnott]

Fair enough. But I am seeing all the same symptoms, he is seeing for my project where I do you have to specify that extra dependency data.

[jasonmalinowski]

@Pilchie: as far as triaging this, who should be assigned first? It's quite possible all the various symptoms were seeing here are from some root cause.

[yishaigalatzer]

@Pilchie ping. I'm assigning to @jasonmalinowski as a rep for your team for now. But I don't necessarily expect him to do the work, just a way to put the monkey on someone's shoulder 😈

[rchande]

@yishaigalatzer @jasonmalinowski I have a DevDiv internal bug assigned to me about this.

[rrelyea]

@rchande - can you share bug status and number, please?

[rrelyea]

@rchande - just sent email to follow up.

[nkolev92]

@rrelyea Did you find the bug status and number here?

Closing it as external.