What to do when calling Uninstall-Package without specifying -project parameter

Aug 31, 2010 at 6:31 PM
Edited Aug 31, 2010 at 6:38 PM

Now that we have the concept of default project, an interesting question comes up when users call Uninstall-Package without specifying the –project parameter. Do we

  • Uninstall the package from the default project (which is parallel to the Install-Package command), OR
  • Uninstall the package from all projects (which is the current behavior)? If we go this route, then we will need to provide a switch –allprojects to the command to allow uninstalling from all projects in the solution.

Thoughts?

-Luan

Aug 31, 2010 at 6:34 PM
Also do we trickle the dependencies into dependent projects?

-d

On Aug 31, 2010, at 12:31 PM, "dotnetjunky" <notifications@codeplex.com> wrote:

From: dotnetjunky

Now that we have the concept of default project, an interesting question comes up when users call Uninstall-Package without specifying the –project parameter. Do we:

· Uninstall the package from the default project (which is parallel to the Install-Package command), OR

· Uninstall the package from all projects (which is the current behavior)? If we go this route, then we will need to provide a switch –allprojects to the command to allow uninstalling from all projects in the solution.

Thoughts?

-Luan

Aug 31, 2010 at 6:37 PM

By default, no.

There is a switch parameter –RemoveDependencies to do that.

From: drusellers [mailto:notifications@codeplex.com]
Sent: Tuesday, August 31, 2010 10:35 AM
To: Luan Nguyen
Subject: Re: What to do when calling Uninstall-Package without specifying -project parameter [nupack:225497]

From: drusellers

Also do we trickle the dependencies into dependent projects?

-d


On Aug 31, 2010, at 12:31 PM, "dotnetjunky" <notifications@codeplex.com> wrote:

From: dotnetjunky

Now that we have the concept of default project, an interesting question comes up when users call Uninstall-Package without specifying the –project parameter. Do we:

· Uninstall the package from the default project (which is parallel to the Install-Package command), OR

· Uninstall the package from all projects (which is the current behavior)? If we go this route, then we will need to provide a switch –allprojects to the command to allow uninstalling from all projects in the solution.

Thoughts?

-Luan

Read the full discussion online.

To add a post to this discussion, reply to this email (nupack@discussions.codeplex.com)

To start a new discussion for this project, email nupack@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

Aug 31, 2010 at 6:37 PM

Uninstall-Package should only apply to the current (or explicitly specified) project.  This makes the command symmetrical with Install-Package.

As far as uninstalling dependencies, we do have some switches to drive this, though I think there is some more tweaking to do there.

Aug 31, 2010 at 6:40 PM

Agree with @davidebb, Uninstall-Package should only be for the default one or if you specify a project. Maybe we should add Uninstall-AllPackages cmdlet that would be explicit in removing it from all projects.

Aug 31, 2010 at 6:42 PM

IIRC setting a default project is always explicit, so it seems reasonable to assume that for the -Project argument when not specified (and when uninstalling a package with a project-level footprint). It might be nice, if when we did so, we prominently display a message in the result that says something like, "Uninstalled from <default>, but still installed in <other projects>; use -Project flag to specify" when projects other than the default have the package and we used on the default.

Aug 31, 2010 at 6:44 PM
bsimser wrote:

Agree with @davidebb, Uninstall-Package should only be for the default one or if you specify a project. Maybe we should add Uninstall-AllPackages cmdlet that would be explicit in removing it from all projects.

 Rather than adding a new Uninstall-AllPackages command, we can simply add a switch parameter -allprojects to Uninstall-Package, as I mentioned in the first post. Agree?

Aug 31, 2010 at 6:46 PM

Yup, that would be good too (I thought about that right after sending the last message)

From: dotnetjunky [mailto:notifications@codeplex.com]
Sent: Tuesday, August 31, 2010 11:44 AM
To: Simser, Bil
Subject: Re: What to do when calling Uninstall-Package without specifying -project parameter [nupack:225497]

From: dotnetjunky

bsimser wrote:

Agree with @davidebb, Uninstall-Package should only be for the default one or if you specify a project. Maybe we should add Uninstall-AllPackages cmdlet that would be explicit in removing it from all projects.

Rather than adding a new Uninstall-AllPackages command, we can simply add a switch parameter -allprojects to Uninstall-Package, as I mentioned in the first post. Agree?

Read the full discussion online.

To add a post to this discussion, reply to this email (nupack@discussions.codeplex.com)

To start a new discussion for this project, email nupack@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com

Aug 31, 2010 at 6:50 PM
Sorry. I was thinking on Add

-d

On Aug 31, 2010, at 12:37 PM, "dotnetjunky" <notifications@codeplex.com> wrote:

From: dotnetjunky

By default, no.

There is a switch parameter –RemoveDependencies to do that.

From: drusellers [mailto:notifications@codeplex.com]
Sent: Tuesday, August 31, 2010 10:35 AM
To: Luan Nguyen
Subject: Re: What to do when calling Uninstall-Package without specifying -project parameter [nupack:225497]

From: drusellers

Also do we trickle the dependencies into dependent projects?

-d


On Aug 31, 2010, at 12:31 PM, "dotnetjunky" <notifications@codeplex.com> wrote:

From: dotnetjunky

Now that we have the concept of default project, an interesting question comes up when users call Uninstall-Package without specifying the –project parameter. Do we:

· Uninstall the package from the default project (which is parallel to the Install-Package command), OR

· Uninstall the package from all projects (which is the current behavior)? If we go this route, then we will need to provide a switch –allprojects to the command to allow uninstalling from all projects in the solution.

Thoughts?

-Luan

Read the full discussion online.

To add a post to this discussion, reply to this email (nupack@discussions.codeplex.com)

To start a new discussion for this project, email nupack@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at codeplex.com