Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
So when planning new projects is it safe to use NuPack to handle dependencies? When I say safe, will it stick around? Or is it going to just be a hyped project that dies (i.e. Google Wave)? Is there really a place, or need for dependency management in .NET?
If not, what is the recommended way to handle dependencies?
NuPack is currently a developer preview but a) it’s actively developed and maintained by both OSS developers (like myself) and core ASP.NET Microsoft employees and b) it will be folded into the core of Visual Studio. So yes, it will be around for a long time.