Have you figured out a way to run the nuget powershell extensions outside of visual studio? I tried importing the module into a regular powershell console, and it complained that they were built against .net 4.0 instead of .net 2.0. Maybe there is a way to run Powershell in .net 4.0, I haven't found it. This really turned me off of Nuget. I hope I'm mistaken and there is a way to run the commands from a regular powershell console.
On Thu, Jan 13, 2011 at 9:33 AM, Paul McCallick <[email protected]> wrote: > This list introduced me to nu, which uses gem to do package management in a > .net friendly way. Nice. Apparently, nu begat nuGet, and the nu > contributers shifted focus to nuGet. > nuGet doesn't fit our desired workflow. It assumes that you're going to > store binaries in source control, and doesn't play well outside of visual > studio. I find this odd, as nu worked great within our desired workflow. > Thoughts on this? Anyone care to share their way of doing it? > In particular we are struggling with dependency management. Binary A > references binaries B. Both A and B reference C. Fred wants to work on A, > and needs to make sure he has the right versions of B and C. The build > machine wants to build and test A... > > -- > --Paul > > -- > You received this message because you are subscribed to the Google Groups > "Seattle area Alt.Net" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/altnetseattle?hl=en. > -- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
