6

I've recently upgraded my VisualStudio 2010 installation with NuGet 2.0 and it seems that this breaks the MvcScaffolding package from Hanselman and Kirkland. Whenever I attempt to build a new controller and views w/ repositories, I get a MethodInvocationError during scaffolding. Specifically, System.Management.Automation.MethodInvocationException calling "Execute" with "5" arguements. Object reference not set to an instance of an object. According to the stack trace, this is happening at the NuGet.PackageExtensions.GetFiles() method. Of course, the final statement in the stack dump is "You may need to upgrade to a newer version of MvcScaffolding", but I've determined that this is appended to the end of all the errors. I'm currently using v1.0.7 of the MvcScaffolding package, which is the latest. Anyone have any thoughts on why this is happening, and better yet, how to get around it? Thanks.

tereško
  • 58,060
  • 25
  • 98
  • 150
Scott Mayfield
  • 2,254
  • 2
  • 20
  • 28
  • I'm having the same problem - I hope there is an answer to this! – asgeo1 Jul 04 '12 at 04:45
  • 1
    I find if I use the NuGet console, I can create the controller OK. It's just the GUI integration that is not working for me. – asgeo1 Jul 04 '12 at 06:13

1 Answers1

0

This appears to be still the case, also with VS2012 and the latest mvcscaffolding package. However as commented in other threads, running the commands in package manager console window does work. The blog by stevesanderson has syntax details

Tim
  • 7,401
  • 13
  • 61
  • 102