This question is locked. New answers and comments are not allowed.
Hi,
I started evaluation JustCode and thus far I am very happy with it.
One "Warning" that is reported erroneously IMHO is a XAML warning for "XAML: Unknown property 'X' of type 'Foo'"
This happens if I define a standard Attached Behavior as follows:
I hope there are no nasty typos in the above example. We now have a basic attached property wrapped in a class. This behavior obviously does nothing, but we don't need that for the example.
JustCode will now generate the warning cited above (namespacing etc. omitted for brevity)
XAML: Unknown property 'X' of type 'Foo'
The issue is obviously that JustCode is looking for the CLR properties to back the X property - but those are not present in the case of attached properties / attached behaviors.
See also http://msdn.microsoft.com/en-us/library/ms749011.aspx
Or am I missing something really basic here.
Cheers,
Jan
I started evaluation JustCode and thus far I am very happy with it.
One "Warning" that is reported erroneously IMHO is a XAML warning for "XAML: Unknown property 'X' of type 'Foo'"
This happens if I define a standard Attached Behavior as follows:
public
class
Foo
{
public
static
readonly
DependencyProperty XProperty =
DependencyPropery.RegisterAttached
(
"X"
,
typeof
(
object
),
typeof
(Foo),
new
UIPropertyMetaData(
null
));
public
static
void
SetX(DependencyObject target,
object
value)
{
target.SetValue(XProperty, value);
}
public
static
void
GetX(DependencyObject target)
{
return
target.GetValue(XProperty);
}
}
I hope there are no nasty typos in the above example. We now have a basic attached property wrapped in a class. This behavior obviously does nothing, but we don't need that for the example.
JustCode will now generate the warning cited above (namespacing etc. omitted for brevity)
XAML: Unknown property 'X' of type 'Foo'
The issue is obviously that JustCode is looking for the CLR properties to back the X property - but those are not present in the case of attached properties / attached behaviors.
See also http://msdn.microsoft.com/en-us/library/ms749011.aspx
Or am I missing something really basic here.
Cheers,
Jan