nunit-core team mailing list archive

[Chad Kittel <chad.kittel@xxxxxxxxx>]

Thank you for not abandoning it.  I'm no longer affected by this
personally, because I have moved on to a different team, using a
different technology (C#).  That said, the team I left is still
constrained by this limitation of course.

I too really like Option #3, even if it's a pollution an otherwise clean
/straight-forward overload chain, it would allow the team to move
forward and no longer be locked into the last supported version.  It
kicks the can down the road without ignoring the problem within the
framework.  It's a trap door for those that need it, and can be ignored
by those that don't.  The IntelliSense comment should probably explain
that this isn't method isn't designed for "typical" usage.

-- 
You received this bug notification because you are a member of NUnit
Core Developers, which is the registrant for NUnit Framework.
https://bugs.launchpad.net/bugs/498690

Title:
  Assert.That() doesn't like properties with scoped setters

Status in NUnit Test Framework:
  Triaged
Status in NUnit V2 Test Framework:
  Triaged

Bug description:
  Public Class SomeClass
      Public Property BrokenProp() As String
          Get
              Return String.Empty
          End Get
          Private Set(ByVal value As String)
          End Set
      End Property
  End Class

  <TestFixture()> Public Class clsTestTask
      <Test()> Public Sub TestXyz()
          Dim obj As New SomeClass()
          Expect(obj.BrokenProp, EqualTo(String.Empty))
      End Sub
  End Class

  The above code produces a compiler error:
  Error 1 'Set' accessor of property 'BrokenProp' is not accessible.

  If the scoping wasn't applied to the setter on the property or the property
  was ReadOnly, the compile error goes away.

  This is a .NET 2.0 assembly, compiled with the Visual Studio 2008 SP1.

  NUnit 2.4.7 and prior did not experience this issue.

  BTW, I've also started a Google Group posting for this issue:
  http://groups.google.com/group/nunit-discuss/browse_thread/thread/edb56db3d3e60195

  [From SF:2792355]

  SF Comment:
  More info... the equivalent scoped setter in C# does not have this problem.
  It arises solely with VB.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/498690/+subscriptions