packages.config

Is there an alternative to contentFiles with projects that use packages.config?

夙愿已清 提交于 2021-02-04 19:51:05
问题 I have a nuget package with content that I want to be copied to the build output when users install my package. There is support for this: NuGet ContentFiles Demystified in NuGet v3.3. However, it only works in projects that use project.json . The contentFiles are not copied to my build output when I have a project that uses packages.config . Is there an alternative or workaround I could use in order to make my NuGet package work on projects that use either a project.json or packages.config ?

Cannot load file or assembly 'Microsoft.Extensions.Configuration.Abstractions, Version=3.1.0.0' in MSTest project

有些话、适合烂在心里 提交于 2021-01-29 02:10:48
问题 I'm having problem with MSTest, Here the issue Open VS2019 Make sure that package management is set to [PackageReference] Create a .Net Framework test project Add Nuget package Microsoft.Extentions.Configuration last version (3.1.3.0) Add the code below Run test ==> Test fail with error [Cannot load file or assembly Microsoft.Extensions.Configuration.Abstractions, Version=3.1.0.0 ...] error PS : using package.config instead of PackageReference solve the issue. Downgrading to Microsoft

Cannot load file or assembly 'Microsoft.Extensions.Configuration.Abstractions, Version=3.1.0.0' in MSTest project

百般思念 提交于 2021-01-29 02:08:57
问题 I'm having problem with MSTest, Here the issue Open VS2019 Make sure that package management is set to [PackageReference] Create a .Net Framework test project Add Nuget package Microsoft.Extentions.Configuration last version (3.1.3.0) Add the code below Run test ==> Test fail with error [Cannot load file or assembly Microsoft.Extensions.Configuration.Abstractions, Version=3.1.0.0 ...] error PS : using package.config instead of PackageReference solve the issue. Downgrading to Microsoft

Switch back to packages.config - clarification on answer

一曲冷凌霜 提交于 2019-12-24 00:36:35
问题 In line with the rules, I have to ask a new question, to get some clarification on another question/answer. This answer is this one: https://stackoverflow.com/a/45964469/305916 Then what? Just did the accepted answer, but the packages.config file is not populated with the packages (I know it doesn't say so). I am missing what to do next if the packages appear automatically in the packages.config or I need to install them again... I am leaning towards the latter, but I feel the answer is not

NuGet.exe install error 9009 - Downloaded Git repo won't build - mono--runtime=v4.0.30319

怎甘沉沦 提交于 2019-12-12 01:53:10
问题 I'm not the most experienced programmer so please excuse any information that is irrelevant here. Better for me to put as much detail down as I can. I'm working with a team solution in Visual Studio 2013 on windows, and just recently we had some issues to do with NuGet packages. Another member of my team solved the issue by reinstalling a package "Microsoft.AspNet.WebApi". I have now pulled the latest version and it won't build on my machine, although it does on my team members machine. It

Switch back to packages.config

限于喜欢 提交于 2019-12-10 01:23:57
问题 Is it possible to switch back to packages.config scheme of things? I moved to PackageReference scheme when I created the project, but for some reasons need to move to old way of things now. I have tried Package Manager Console commands like restore with Update and Reinstall options. They do not generate packages.config anymore. I also switched Tools > Options > NuGet Package Manager to packages.config . No good. 回答1: You'll need to: Add an "empty" packages.config file to the project (that is,

Switch back to packages.config

夙愿已清 提交于 2019-12-04 22:54:02
Is it possible to switch back to packages.config scheme of things? I moved to PackageReference scheme when I created the project, but for some reasons need to move to old way of things now. I have tried Package Manager Console commands like restore with Update and Reinstall options. They do not generate packages.config anymore. I also switched Tools > Options > NuGet Package Manager to packages.config . No good. You'll need to: Add an "empty" packages.config file to the project (that is, xml as in the example but without individual <package> elements) Unload the project or close vs and open