NuGet/Home

.targets/.props in build/ folder are not added to a (non-C#) CPS-based project upon package install

Open

#1,850 opened on Dec 17, 2015

View on GitHub
 (14 comments) (5 reactions) (0 assignees)HTML (292 forks)batch import
Priority:3Type:Bughelp wanted

Repository metrics

Stars
 (1,459 stars)
PR merge metrics
 (Avg merge 464d 23h) (1 merged PR in 30d)

Description

I have a CPS-based project type for a custom Language (not C# or VB). This project type reports the AssemblyReferences, DeclaredSourceItems, and UserSourceItems capabilities. I also created a NuGet package that just contains minimal .targets/.props in the build/ folder.

If I install this NuGet package to a C# Class Library project, the .targets/.props are successfully added to the .csproj.

However, if I install this NuGet package to my CPS project type, no .targets/.props are added to the project file (.sfproj).

I am using NuGet 3.3.0 both to create my package, and to install it.

Contributor guide

Research direction
Investigate why .targets/.props are not imported for CPS projects. Check the NuGet import mechanism and compare with C# projects. Look for differences in how CPS projects handle package imports.
Tech stack
csharp
Domain
build systemtooling
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
NuGetMSBuildVisual Studio Extensibility
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30