Note that the Output path set in the 1st property group which is conditionless should have been inherited and used even if other property groups don't have it.
Also I couldn't produce this kind of project file with vs2010 as originally suggested. Though these are valid files and can be encountered in the wild. ** Attachment added: "sample project that reproduces the bug." https://bugs.launchpad.net/nunitv2/+bug/806198/+attachment/2202443/+files/TestOP.zip ** Summary changed: - nunit console crashes when opening vs2010 projects. Expects a outputpath in every propertygroup + nunit console crashes when opening certain projects with common output path. Expects a outputpath in every propertygroup -- You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. https://bugs.launchpad.net/bugs/806198 Title: nunit console crashes when opening certain projects with common output path. Expects a outputpath in every propertygroup Status in NUnit V2 Test Framework: Triaged Bug description: in VS2010 created projects, not every PropertyGroup has a output path set. However the nunit LoadMSBuildProject function attempts to look for output path in every property group and crashes with a null reference exception. To manage notifications about this bug go to: https://bugs.launchpad.net/nunitv2/+bug/806198/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~nunit-core Post to : [email protected] Unsubscribe : https://launchpad.net/~nunit-core More help : https://help.launchpad.net/ListHelp
