c# - Adding an Existing Solution that was Previously a NuGet Package into a Single Solution -
i'm working on stabilizing rather old website development can resume on adding new features. previous implementers had rather strange approach modularity - heart in right place, execution was... off.
there's 1 "main" solution, - front end guy, typically work with. includes web project served iis. lot of (pretty all) end stuff however, brought in via nuget package private nuget server (teamcity)
now. seems kind of nice , modular until have make backend change. previously, if backend change required, team make change in backend solution, , commit , republish entire package. front end solution must update nuget package on it's end in order receive changes.
this nightmare...
i won't start on version control situation. lets branching hasn't been known concept here number of years. i'm here put on straight , narrow.
i wondering if has had experience adding , existing project solution nuget package. added entire backend solution , removed nuget dependency, build blow in face declaring types backend solution no longer existed.
i'm thinking need add these new projects build order or something? maybe that's red herring.
yours sincerely,
a javascript guy who's out of depth .net...
have added references "new" backend in front-end project? right-click on project add -> reference... , select backend project within solution list.
Comments
Post a Comment