# Bad NuGet install parameter in latest beta

**URL:** https://www.finalbuilder.com/forums/t/bad-nuget-install-parameter-in-latest-beta/5913
**Category:** Bugs
**Created:** [July 24, 2014, 7:02am UTC](https://www.finalbuilder.com/forums/t/bad-nuget-install-parameter-in-latest-beta/5913 "2014-07-24T07:02:42Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![drewpeterson](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/drewpeterson/32/158_2.png) [@drewpeterson](https://www.finalbuilder.com/forums/u/drewpeterson)
#### Post date: [July 24, 2014, 7:02am UTC](https://www.finalbuilder.com/forums/t/bad-nuget-install-parameter-in-latest-beta/5913/1 "2014-07-24T07:02:42Z")

</div>

In the latest beta, Nuget install actions pass the FileConflictAction parameter, which is not supported with the version of Nuget that ships with the agent (or the latest, 2.8.2).  
  
It’s odd because it’s still listed in the command-line documentation on the NuGet site, but the action fails because the parameter is not supported.

---

<div class="post-metadata">

### Author: ![Sparky](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/sparky/32/10_2.png) [@Sparky](https://www.finalbuilder.com/forums/u/Sparky)
#### Post date: [July 25, 2014, 3:17am UTC](https://www.finalbuilder.com/forums/t/bad-nuget-install-parameter-in-latest-beta/5913/2 "2014-07-25T03:17:22Z")

</div>

Hi Drew,  
  
Thanks for reporting this. It seems that the NuGet install command line never supported this option. The option has been removed from the latest beta.

---

<div class="post-metadata">

### Author: ![drewpeterson](https://www.finalbuilder.com/forums/user_avatar/www.finalbuilder.com/drewpeterson/32/158_2.png) [@drewpeterson](https://www.finalbuilder.com/forums/u/drewpeterson)
#### Post date: [July 25, 2014, 9:55am UTC](https://www.finalbuilder.com/forums/t/bad-nuget-install-parameter-in-latest-beta/5913/3 "2014-07-25T09:55:54Z")

</div>

This is fixed now, thanks.
