You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> Paket enabled us to share code between repositories and solutions without the need to create new packages every time something changed.
124
124
125
-
[Rhein-Spree](https://www.rhein-spree.com) is a Berlin based software services company with additional employees in Leipzig and Düsseldorf. We are focused on .NET Technologies with great results.
125
+
[Rhein-Spree](https://www.rhein-spree.com) is software services and consulting company from Berlin with teammates in Leipzig, Dresden and Düsseldorf. We are focused on .NET Technologies with great results.
126
126
127
-
However, when it comes to dependency management in bigger repositories with multiple solutions we
128
-
felt the pain of the inconsistent resolition of package versions across the repository. It got
129
-
even harder as the solutions grow. At some point we decided to give Paket a try and what should
130
-
we say. We had some work in getting the dependencies file correct and then in worked like a
127
+
When it comes to dependency management in growing environment with multiple solutions etc. we
128
+
felt the pain of inconsistent resolution of package versions across the repository. It got
129
+
even harder as the solutions grew. At some point we decided to give Paket a try and what should
130
+
we say... We had some work in getting the dependencies file correct and then it worked like a
131
131
charm. Even better. We also started to use the git functionality of Paket in referencing other
132
132
git repositories. This enabled us to share code between repositories and solutions without the
133
133
need to create new packages everytime something changed.
134
134
135
+
So the time we needed to resolves versioning issues has decreased tremendously.
0 commit comments