[jira] [Assigned] (IGNITE-4980) .NET: NuGet packages do not work with PackageReference in VS2017

[Pavel Tupitsyn (Jira)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-4980:
--

Assignee: Pavel Tupitsyn

> .NET: NuGet packages do not work with PackageReference in VS2017
> 
>
> Key: IGNITE-4980
> URL: https://issues.apache.org/jira/browse/IGNITE-4980
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>Assignee: Pavel Tupitsyn
>Priority: Major
>  Labels: .NET
>
> VS2017 & NuGet 4.0 come with a new way of referencing packages: instead of 
> {{packages.config}}, there is a {{PackageReference}} section in {{csproj}} 
> file: 
> http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html
> This feature does not support {{install.ps1}} script which we use to insert 
> build event for copying JARs to output directory.
> This is not a blocker, since build event can be set up manually.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Assigned] (IGNITE-4980) .NET: NuGet packages do not work with PackageReference in VS2017

[Pavel Tupitsyn (JIRA)]

 [ 
https://issues.apache.org/jira/browse/IGNITE-4980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Pavel Tupitsyn reassigned IGNITE-4980:
--

Assignee: (was: Pavel Tupitsyn)

> .NET: NuGet packages do not work with PackageReference in VS2017
> 
>
> Key: IGNITE-4980
> URL: https://issues.apache.org/jira/browse/IGNITE-4980
> Project: Ignite
>  Issue Type: Bug
>Affects Versions: 1.6
>Reporter: Pavel Tupitsyn
>  Labels: .NET
> Fix For: 2.1
>
>
> VS2017 & NuGet 4.0 come with a new way of referencing packages: instead of 
> {{packages.config}}, there is a {{PackageReference}} section in {{csproj}} 
> file: 
> http://blog.nuget.org/20170316/NuGet-now-fully-integrated-into-MSBuild.html
> This feature does not support {{install.ps1}} script which we use to insert 
> build event for copying JARs to output directory.
> This is not a blocker, since build event can be set up manually.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)