It sounds to me like a tremendously large number of variables in play at once and a large number of things potentially NOT in a run-able/dependable state.
Although your end-state (MVC3, VS2010, .NET4, and RM 3.6) is in use by many without issue (myself included), I would start by trying to better isolate the number of things you're trying to deal with at once in re: your fault-isolation process. I know from past experience with some of the 'auto-upgraders' that took ppl from MVC1 to MVC2 that they are not without issue and don't always work with 100% reliability. I cannot speak from experience re: if the same is likely to be true of MVC2-->MVC3 conversions. Perhaps start a new MVC3 project and bring your MVC2 content into the new MVC3 project rather than trying to do an in-place upgrade --? Also, try a different test-runner (e.g., if NUnit, try the stand-alone NUnit GUI runner) and see if that makes a difference. MANUALLY delete the contents of all /bin/ and /obj/ folders (do NOT rely on the CLEAN SOLUTION command from VS) and then do a complete rebuild and see if that makes a difference. Hope this helps--! Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Mon, Mar 14, 2011 at 3:47 PM, tvanfosson <[email protected]> wrote: > I have an ASP.NET MVC 2.0 project started in VS2008 and updated to > VS2010, but not to .NET 4.0. Now when I start up a unit testing > (using the test runner from TestDriven.NET), it takes an insanely long > time to generate mocks using Rhino.Mocks 3.6. If I "Break All" I can > tell that it's stuck either in GenerateMock() or GenerateStub(). > Eventually, like minutes later per test, it will eventually get past > this and the test will run, but it's a pain. > > I don't see this behavior with new MVC 2.0 projects started in VS2010 > or MVC 3.0 projects, just this one legacy project that I've migrated. > > Any ideas? I've tried removing/adding references, including switching > to using Rhino.Mocks from NuGet to no avail. > > This may be related but I'm also unable to switch to using .NET 4.0. > Trying that resulted in an inability to find one of my project > libraries during compilation. After spending a day trying to resolve > what I assumed was project file corruption, I rolled those changes > back and resorting to trying to get Rhino.Mocks to work with my > VS2010/.NET 3.5/MVC2 project. > > -- > You received this message because you are subscribed to the Google Groups > "Rhino.Mocks" 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/rhinomocks?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Rhino.Mocks" 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/rhinomocks?hl=en.
