Add support for Attribute properties/values

Not sure why we can only deal with a string version of the attribute value… makes it hard to reliably parse the properties of an attribute.

For example:

[Route("foo", Name = "foo")]
public ActionResult Do() {
}

[Route("foo", Order = 1, Name = "foo")]
public ActionResult Do() {
}

[Route("foo")]
public ActionResult Do() {
}

We can do string manipulation but it seems better if Typewriter just exposed a PropertyCollection.

[minawalphonce]

+1 for this feature. I have a problem which is kind of related. I’m using the attribute ResponseType on top of my webapi methods. I got the type as string this way e.g. “typeof(System.Collections.Generic.IEnumerable<FullClassName>)” if it s a collection. now i need a way to convert this string to Type. System.Type.GetType simply not working of course.

[frhagn]

Hi @kamranayub, Typewriter behaves this way because of limitations in Visual Studio 2013 where the CodeDom provider only returns a string instead of a useful object. I’ve started work on a new Visual Studio 2015-only version of Typewriter where this kind of limitations can be removed.