[Nunit-core] [Bug 517187] Re: Unexpected Config File Name Used When Opening csproj File

2010-04-19 Thread Charlie Poole
** Changed in: nunitv2 Status: Triaged = Fix Committed -- Unexpected Config File Name Used When Opening csproj File https://bugs.launchpad.net/bugs/517187 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit V2

[Nunit-core] [Bug 517187] Re: Unexpected Config File Name Used When Opening csproj File

2010-04-19 Thread Launchpad Bug Tracker
** Branch linked: lp:nunitv2 -- Unexpected Config File Name Used When Opening csproj File https://bugs.launchpad.net/bugs/517187 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit V2 Test Framework: Fix Committed

[Nunit-core] [Bug 517187] Re: Unexpected Config File Name Used When Opening csproj File

2010-04-12 Thread Charlie Poole
** Changed in: nunitv2 Milestone: None = 2.5.5 -- Unexpected Config File Name Used When Opening csproj File https://bugs.launchpad.net/bugs/517187 You received this bug notification because you are a member of NUnit Developers, which is subscribed to NUnit V2. Status in NUnit V2 Test

[Nunit-core] [Bug 517187] Re: Unexpected Config File Name Used When Opening csproj File

2010-02-06 Thread Charlie Poole
To clarify the situation, NUnit is working internally with a project nunit.tests.nunit - or at least that's what it would be called if you were to save it. However, the docs say nothing about this, and the need to add csproj to the name was not an intended affect. We should check to see when this