10
votes
Get license information for all used NuGet packages
Based on multiple sources, I've made a PowerShell script that reads all NuGet packages and fetches the license files and put that in a folder called "licenses". The script should be run on ...
- 211
6
votes
Accepted
Should a solution containing projects exposed as nuget reference them as package?
If I got this right, as soon as you replace the nuget reference from B to A by a project reference, there is no project left which consumes A as a nuget package, right?
So if there is no consumer any ...
- 221k
6
votes
Accepted
Alternative for C# Library distribution within an Organisation
Not long ago, I wrote this answer which scetches the typical process for library reuse among different projects. From that answer, it should be clear, what you experience is
mainly a process issue, ...
- 221k
6
votes
One project per solution to create nuget packages
I'm using Azure DevOps (formerly VSTS), and while this question is old, it may have value for others.
My understanding of best practice is:
Use semantic versioning
Separate package groups into ...
- 161
5
votes
Accepted
When to create a nuget package vs creating a web api
If its a pure function then you want the code to execute on the same CPU as the app. a nuget package is a good way of getting that code into your project.
If the function has side effects that you ...
- 84.6k
5
votes
Accepted
Single massive solution - good idea?
As with everything, there are trade-offs. There is one project my team has to develop that is similar, but in some ways worse. All the project names look similar, and the folders they are shoved in ...
- 46.5k
5
votes
How to implement automatic SemVer from code changes
In the comments, amon is absolutely right that just changing the interfaces is insufficient to determine if behavior is backwards compatible. I find it highly unlikely that you would be able to build ...
- 85.9k
5
votes
Best practices for team development with NuGet projects in .Net
Tangent: your project structure
First of all, a massive elephant that is proving to be a bit of a distraction / cause for general concern: if I understand your explanation correctly, you have ...
- 59.5k
4
votes
Single massive solution - good idea?
I find structure you describe as extremely problematic. I understand why someone would make this kind of project structure. But I believe that it is just a workaround the real problem, not a solution.
...
- 38.2k
3
votes
Accepted
Strategies to organize multiple projects which may reference each other and managed by different teams in Git?
Before thinking about the tools, I would recommend to have a look at the process.
With multiple projects managed by multiple teams, if you don't want the teams and projects tied to each other, from an ...
- 221k
3
votes
Single massive solution - good idea?
Some excellent answers here already, but let me focus on what you mentioned to be your main issue, getting the build working on another machine.
This should be mostly orthogonal to any of the other ...
- 221k
3
votes
Accepted
Should libraries be packaged together based on similar traits?
You shouldnt bundle libraries together into packages at all.
Put each library in its own package and use the nuspec dependencies to indicate if one relies on another
- 84.6k
3
votes
When to create a nuget package vs creating a web api
Use NuGet when your project, library or framework needs to be publicly distributed to software developers outside of your organization. *
Use a web API when you need the benefits that a web API ...
- 201k
3
votes
Accepted
Best practices for developing NuGet package alongside consumer?
NuGet has the ability to point to any file system location. It will treat this directory as a local repository. Publish here during your dev cycle.
The other thing you’ll want to do is automate the ...
- 9,021
3
votes
Accepted
How to share common NuGet package settings between projects (csproj 2017)
That's simple to achieve: use a Directory.Build.props file in the solution folder and put those values in there. It takes the following format (just like the new .csproj files):
<Project>
&...
- 39.6k
3
votes
Accepted
Is It Considered Good Practice to Use Dependency Injection with Strategies from a NuGet Package?
Your library should be stand-alone. It should work without any kind of dependency injection container, because that is an implementation detail of the application and a library should not care.
I ...
- 9,230
3
votes
Accepted
Advice on Developing Shared Public Libraries in Visual Studio
I think you've positioned yourself inbetween two workable scenarios and the hassle you're dealing with now is the result of not sticking to one scenario in particular.
You're using Nuget packages, ...
- 59.5k
2
votes
Best practices for developing NuGet package alongside consumer?
I think 'best practice' is to develop the nuget package by itself, with enough tests to ensure that you can consume it without having to debug.
But I do know what you mean. I think the common work ...
- 84.6k
2
votes
NuGet on VSTS strategy
VSTS can create Nuget Feeds. You can host your own feed and publish your packages there. You may want to have two feeds, one for release packages and one for your internal debugging needs.
You can ...
- 9,230
2
votes
Accepted
NuGet versioning with gitflow
By far the easiest way to handle this is to use a local package source.
If you make .net standard class libraries you can package them automatically after each build in VS. I guess you could automate ...
- 84.6k
2
votes
Accepted
Avoid or minimize merge conflicts while using NuGet and GitFlow
OK Here's my guess.
You have a shared lib distributed by nuget and consumed by you application.
When you get a feature request for the application you create a new feature branch on its repo, but ...
- 84.6k
2
votes
Accepted
How to test for backwards compatibility in NuGet?
Package authors should be respecting compatibility with the proper use of the package version. What you're intending to do sounds like it would be a lot of work if at all possible. Your project using ...
- 146
2
votes
Risk of NuGet package adding new reference DLL
Whenever you include 3rd party components in your own software system, updates for those components can break your system, whether those updates include a new DLL or not.
This happens even if the ...
- 221k
2
votes
Accepted
NuGet Hell - by design our NuGet repo doesn't yet include the new functionality we reference
I am not an expert on NuGet and have only limited experience with "nuget.exe", but I am pretty sure I understood what your actual problem is, and I think the following may be a conceptual solution:
...
- 221k
2
votes
Publishing packages for personal and commercial use
In most jurisdictions, software that was written as part of your employment duties (aka your job) belongs to your employer. That means that you are not allowed to publish that software in any way ...
1
vote
Azure DevOps Change nuget.config in CI/CD process
I would like to expand on Ben Cottrell's comment, but present you with a fork in the road when it comes to implementing the build pipelines.
My instinct makes me question the need for a NuGet package ...
- 46.6k
1
vote
Should a solution containing projects exposed as nuget reference them as package?
Generally speaking, if project A is published as a nuget package then consume it as a nuget package.
Now, we all know that if you are editing B and A together, its just easier to do a direct ...
- 84.6k
1
vote
NuGet Hell - by design our NuGet repo doesn't yet include the new functionality we reference
If you are going to test this way you are going to need to be more nuanced about it.
I'm going to presume that the actual library being released to nuget must pass these tests that you are releasing ...
- 16.6k
1
vote
working with multiple libraries and versions using nuget local feed
If I understand your problem correctly, you can solve it by using a single nuget feed and prerelease version numbers.
Nuget supports Semver 2.0.0, this means you can publish your debug or ...
1
vote
Structuring dependencies for .Net core across Nuget packages
I know this pain well. Ran into this same issue at my company and we have almost 40 libraries that are managed in a similar regard. Redeploying the chain of them takes considerable tedious manual ...
Only top scored, non community-wiki answers of a minimum length are eligible