<p>I'd recommend <a href="http://inedo.com/proget" rel="nofollow noreferrer">ProGet</a>. If you're familiar with Artifactory you might find this comparison helpful: <a href="https://inedo.com/support/kb/1115/a-comparison-artifactory-vs-proget" rel="nofollow noreferrer">https://inedo.com/support/kb/1115/a-comparison-artifactory-vs-proget</a> </p>

CC BY-SA 3.0
2017-04-26T17:46:50.543Z
Thanks for your comments...do you think artifacory is a best repo for .NET projects @Karl Harnagy
pandey
CC BY-SA 3.0
2017-04-26T19:45:23.880Z
@pandey "the best for..." is highly subjective, it really depends on what features you need _in addition_ to the nuget artifacts you want to store (assuming here you will package your assemblies with nuget).  Here is another, more complete, comparison of binary repositories.  https://binary-repositories-comparison.github.io/  to know which is best first know what exactly you need and then look for the solution that best fills this need.
Newtopian
CC BY-SA 3.0
2017-04-26T16:22:06.857Z
2017-04-26T16:22:06.857Z
Karl Harnagy
<p>It is wise to think about package management early on.</p>

<p>There are multiple options in terms of package management. The 2 largest are <a href="https://www.jfrog.com/artifactory/" rel="nofollow noreferrer">jFrog Artifactory</a> and <a href="https://www.sonatype.com/nexus-repository-oss" rel="nofollow noreferrer">Sonatype Nexus</a>. Both offer support for multiple formats such as maven, NuGet, Docker, npm, ...</p>

<p>If you only have standard requirements, both of these will suffice. If you have specific requirements, it's best to look at a comparison such as <a href="https://binary-repositories-comparison.github.io/" rel="nofollow noreferrer">this one</a> to find out which one has got what you need.</p>

<p>Both of these offer free versions with all the functionality you will need included.</p>

<p>When it comes to choosing one: If you have experience with one, i would suggest taking that one. Otherwise, you can't really go wrong with either one, since both are widely used by small and large teams around the world.</p>

CC BY-SA 3.0
2017-04-27T06:35:15.413Z
2017-04-27T06:35:15.413Z
Kevin
<p>I am very to new to .NET projects and I am wondering which is the best tool to store binaries of .NET project. How good to store binaries of .NET projects in artifactory and why? can some one answer generally Any comments can be helpful.</p>

<continuous-integration><dotnet><repository>
Best way of binary repository for .NET projects
pandey
# Best way of binary repository for .NET projects

(Asked by: username_0 on 2017-04-26)

I am very to new to .NET projects and I am wondering which is the best tool to store binaries of .NET project. How good to store binaries of .NET projects in artifactory and why? can some one answer generally Any comments can be helpful.

**Tags:** continuous-integration, dotnet, repository


---

## 2 answers

### Answer by username_1 on 2017-04-26. Score: 2

I'd recommend [ProGet](http://inedo.com/proget). If you're familiar with Artifactory you might find this comparison helpful: <https://inedo.com/support/kb/1115/a-comparison-artifactory-vs-proget>

> **Comments:**
> **username_0**: Thanks for your comments...do you think artifacory is a best repo for .NET projects @username_1  
> **username_2**: @username_0 "the best for..." is highly subjective, it really depends on what features you need _in addition_ to the nuget artifacts you want to store (assuming here you will package your assemblies with nuget).  Here is another, more complete, comparison of binary repositories.  https://binary-repositories-comparison.github.io/  to know which is best first know what exactly you need and then look for the solution that best fills this need.  

---

### Answer by username_3 on 2017-04-27. Score: 2

It is wise to think about package management early on.

There are multiple options in terms of package management. The 2 largest are [jFrog Artifactory](https://www.jfrog.com/artifactory/) and [Sonatype Nexus](https://www.sonatype.com/nexus-repository-oss). Both offer support for multiple formats such as maven, NuGet, Docker, npm, ...

If you only have standard requirements, both of these will suffice. If you have specific requirements, it's best to look at a comparison such as [this one](https://binary-repositories-comparison.github.io/) to find out which one has got what you need.

Both of these offer free versions with all the functionality you will need included.

When it comes to choosing one: If you have experience with one, i would suggest taking that one. Otherwise, you can't really go wrong with either one, since both are widely used by small and large teams around the world.


---

