Well, not really a club, but we thought you may wish to have cute ReSharper banner on the side bar of your blog, or project site, or may be print it and put on the wind-screen of your Porsche :) I have one right here, in my blog! Ah, well, I mean banner, not Porsche...
Want it? Go to The Banner Builder page and assemble it as you like. Don't forget to put the result on your website!
28 November 2007
22 November 2007
ReSharper and Visual Studio 2008
Since there is a lot of buzz about Visual Studio 2008 release, I thought I would stand and say about ReSharper in relation to this fact.
Released version
ReSharper 3 can be installed with Visual Studio 2008 and works fine, unless you are using C# 3.0 new features, like lambdas, LINQ, extension methods and such. This constructs are not parsed by ReSharper 3, which was developed to support C# 2.0 only. It is not only highlighting which doesn't support C# 3.0, it is all the core and code intelligence. For example, rename refactoring will not find usages of extension methods and will not update them.
There also could be some glitches, even if you don't use new C# 3.0 constructs. This is due to the fact that C# 3.0 compiler is always used in Visual Studio 2008 C# projects, regardless of target framework. It it is not widely discussed, but changes in language are wider than just several new features. There are differences in type inference in generics and candidates lookup for binding, to name few. If you happen to hit this special cases, ReSharper could behave incorrectly.
If you are really-really going to immediately jump C# 3.0 wagon, you can disable highlighting (Options / Code Inspection / Settings) and switch to Visual Studio native intellisense (Options / Environment / IntelliSense / General). This will help a bit, but still you cannot trust find usages results, refactorings and many other features.
There was also reported weird problem with Visual Studio 2008 and ReSharper installed on x64 computers - opening Visual Studio's Find dialog crashes. We are currently trying to reproduce this problem. If you experience this problem, please tell us!
Some people tend to ask for quick-and-dirty hack for ReSharper 3 so that it just parses the code and don't do anything intelligent with C# 3.0 code. It is not possible. Details are not important here and are pure technical.
Next version
ReSharper 4 is in very active development. Its main purpose is to support C# 3.0 in all of its beauty. This means not only parsing and code intelligence, but also new analysis, refactorings, context actions and quick fixes. We are concentrated on making your development experience with C# 3.0 as smooth and pleasant as possible.
Currently, we have support for implicity typed variables and arrays, extension methods, object and collection initializers and automatic properties. As soon as we complete support for lambdas, queries and anonymous types, we will open Early Access Program. We plan to achieve this goal in January, 2008.
From this point you will be able to download EAP or even nightly builds and try full power of ReSharper 4 with your new C# 3.0 code.
In regards of upgrade policy, we are currently in the process of deciding upgrade cost, who qualifies for free upgrade, or if we want to do something special about this release. I will post about it as soon as I can.
As for release plans, we are aiming at 2008'Q1, hopefully sometime soon after Visual Studio 2008 launch event in February. ReSharper 4 will be available to general public via Early Access Program at least for 2 months before release.
If you have any questions, do not hesitate to ask in comments.
Released version
ReSharper 3 can be installed with Visual Studio 2008 and works fine, unless you are using C# 3.0 new features, like lambdas, LINQ, extension methods and such. This constructs are not parsed by ReSharper 3, which was developed to support C# 2.0 only. It is not only highlighting which doesn't support C# 3.0, it is all the core and code intelligence. For example, rename refactoring will not find usages of extension methods and will not update them.
There also could be some glitches, even if you don't use new C# 3.0 constructs. This is due to the fact that C# 3.0 compiler is always used in Visual Studio 2008 C# projects, regardless of target framework. It it is not widely discussed, but changes in language are wider than just several new features. There are differences in type inference in generics and candidates lookup for binding, to name few. If you happen to hit this special cases, ReSharper could behave incorrectly.
If you are really-really going to immediately jump C# 3.0 wagon, you can disable highlighting (Options / Code Inspection / Settings) and switch to Visual Studio native intellisense (Options / Environment / IntelliSense / General). This will help a bit, but still you cannot trust find usages results, refactorings and many other features.
There was also reported weird problem with Visual Studio 2008 and ReSharper installed on x64 computers - opening Visual Studio's Find dialog crashes. We are currently trying to reproduce this problem. If you experience this problem, please tell us!
Some people tend to ask for quick-and-dirty hack for ReSharper 3 so that it just parses the code and don't do anything intelligent with C# 3.0 code. It is not possible. Details are not important here and are pure technical.
Next version
ReSharper 4 is in very active development. Its main purpose is to support C# 3.0 in all of its beauty. This means not only parsing and code intelligence, but also new analysis, refactorings, context actions and quick fixes. We are concentrated on making your development experience with C# 3.0 as smooth and pleasant as possible.
Currently, we have support for implicity typed variables and arrays, extension methods, object and collection initializers and automatic properties. As soon as we complete support for lambdas, queries and anonymous types, we will open Early Access Program. We plan to achieve this goal in January, 2008.
From this point you will be able to download EAP or even nightly builds and try full power of ReSharper 4 with your new C# 3.0 code.
In regards of upgrade policy, we are currently in the process of deciding upgrade cost, who qualifies for free upgrade, or if we want to do something special about this release. I will post about it as soon as I can.
As for release plans, we are aiming at 2008'Q1, hopefully sometime soon after Visual Studio 2008 launch event in February. ReSharper 4 will be available to general public via Early Access Program at least for 2 months before release.
If you have any questions, do not hesitate to ask in comments.
16 October 2007
C# 3.0 Automatic Properties - Incomplete Feature?
Well, C# 3.0 is nice language. However, digging into details of every new language feature while developing ReSharper support make me wonder about little things that look like incompleteness. Today I'm going to wonder about automatic properties.
This code is correct in C# 3.0, there are no missing "abstract" or get/set bodies. It simply means that compiler will create field and accessors code for you:
What is cool about automatic properties? Obviously, ReSharper users don't benefit much from shorter code - who types properties by hand these days? However there is one very important thing:
If you want to know how this property gets its value, you no longer need to search for both field and property usages. You don't need to synchronize field and property types, once you decide to change it. Also, access to the class attribute (in OOP sense) is fully controlled right at the place of the declaration. You can limit it as you wish:
This way you declare that "Name" can be modified only within the class itself, but can be read from outside.
So, what is missing from this language feature?
Initializer.
I may wish to initilize property to some non-default value. Like this:
Read-only automatic property
In the example above, I don't actually need setter.
Obviously, you don't need read-only automatic property without initializer. Also note, that such property can never change its value, even in constructor, unlike readonly fields.
Attributes on generated fields
If you use simple event form and compiler generates field for storing delegate, you can apply attribute to the generated field by using attribute target:
I wish I could do the same with automatic properties:
Conclusion
Few simple improvements over existing implementation could make automatic properties much more useful in everyday professional .NET development. Unfortunately, language designers decided:
I'd prefer the advanced version, if I had a chance to choose.
public string Name { get; set; }
This code is correct in C# 3.0, there are no missing "abstract" or get/set bodies. It simply means that compiler will create field and accessors code for you:
private string __someGeneratedFieldName;
public string Name
{get { return __someGeneratedFieldName; }
set { __someGeneratedFieldName = value; }
}
What is cool about automatic properties? Obviously, ReSharper users don't benefit much from shorter code - who types properties by hand these days? However there is one very important thing:
Less complexity to manage.
If you want to know how this property gets its value, you no longer need to search for both field and property usages. You don't need to synchronize field and property types, once you decide to change it. Also, access to the class attribute (in OOP sense) is fully controlled right at the place of the declaration. You can limit it as you wish:
public string Name { get; private set; }
This way you declare that "Name" can be modified only within the class itself, but can be read from outside.
So, what is missing from this language feature?
Initializer.
I may wish to initilize property to some non-default value. Like this:
public List<Person> Persons { get; private set; } = new List<Person>();
Read-only automatic property
In the example above, I don't actually need setter.
public List<Person> Persons { get; } = new List<Person>();
Obviously, you don't need read-only automatic property without initializer. Also note, that such property can never change its value, even in constructor, unlike readonly fields.
Attributes on generated fields
If you use simple event form and compiler generates field for storing delegate, you can apply attribute to the generated field by using attribute target:
[field: NonSerialized]public event EventHandler Closed;
I wish I could do the same with automatic properties:
[field: NonSerialized]public List<Person> Persons { get; } = new List<Person>();
Conclusion
Few simple improvements over existing implementation could make automatic properties much more useful in everyday professional .NET development. Unfortunately, language designers decided:
they would work in the "common case" which among other things means no attributes on the generated field. The idea behind that is keeping them simple and not slowly mutating them into full properties.
I'd prefer the advanced version, if I had a chance to choose.
07 September 2007
ReSharper 3.0.3 EAP and Solution-wide Error Analysis
The ReSharper team is actively working on next version with C# 3.0 support, but we are still fixing things for ReSharper 3.0 and even add new features!
Among with various bug-fixes, ReSharper 3.0.3 features "Global Error Analysis" feature that finds compilation errors in your solution on-the-fly. It was available in early ReSharper 3.0 EAP builds, but then we decided that it is not mature enough to put it into release. Now, we've improved it and are going to include it in ReSharper 3.0.3 update.
You can get ReSharper 3.0.3 EAP build at download page. Take a look at post about Early Access Program, if you want to learn more about participating.
To enable analysis of all errors in solution, double-click a red crossing lines symbol at the very right of the status bar and check the "Analyze errors in whole solution" checkbox. Note, that it is per-solution setting. It may take quite a while to analyze your solution for the first time (you can continue your work), but once the solution has been analyzed only those files that may be affected by the changes made are reanalyzed. Tool window with all errors in your solution can be opened using ReSharper | Windows | Errors in Solution menu command. Also, next/previous error command walks through all solution errors, if solution-wide error analysis is enabled.
We would like to hear from you about this feature! Do you like it or not? Does it work fine for you? Do you have any problems? You can leave comments to this post, or drop a message in our EAP newsgroup. Thanks in advance!
Among with various bug-fixes, ReSharper 3.0.3 features "Global Error Analysis" feature that finds compilation errors in your solution on-the-fly. It was available in early ReSharper 3.0 EAP builds, but then we decided that it is not mature enough to put it into release. Now, we've improved it and are going to include it in ReSharper 3.0.3 update.
You can get ReSharper 3.0.3 EAP build at download page. Take a look at post about Early Access Program, if you want to learn more about participating.
To enable analysis of all errors in solution, double-click a red crossing lines symbol at the very right of the status bar and check the "Analyze errors in whole solution" checkbox. Note, that it is per-solution setting. It may take quite a while to analyze your solution for the first time (you can continue your work), but once the solution has been analyzed only those files that may be affected by the changes made are reanalyzed. Tool window with all errors in your solution can be opened using ReSharper | Windows | Errors in Solution menu command. Also, next/previous error command walks through all solution errors, if solution-wide error analysis is enabled.
We would like to hear from you about this feature! Do you like it or not? Does it work fine for you? Do you have any problems? You can leave comments to this post, or drop a message in our EAP newsgroup. Thanks in advance!
06 September 2007
C# 3.0 Collection Initializers - Incomplete Feature?
I was really confused when I learned that "collection initializer" is so limited. I thought it was so natural to support extension methods for "Add" method, but it doesn't.
In short, collection initializer is the following syntax:
Each item in the braces is simply transformed to the call of Add method with appropriate signature.
It's a bit more complex in reality, but it doesn't matter here.
So, when I first saw description of the feature I thought: How cool! I can specify extension method "Add" for "StringBuilder" and get the following:
But, restrictions are too strong - type being constructed should implement IEnumerable and have instance method "Add". IEnumerable is not of a big deal, but inability to use extension methods for Add is deal breaker.
How about this?
No way. You can't use collection initializer for XmlDocument, because it doesn't have Add methods. It is IEnumerable, though.
May be this?
No way. PermissionSet is IEnumerable too, but does have AddPermission instead of Add method.
If it only were searching for candidates as follows:
This change, or something similar, would turn the otherwise very limited collection initializers into really powerfull object initialization feature.
In short, collection initializer is the following syntax:
var list = new List<int> { 1, 2, 3 };
var dic = new Dictionary<int,string> { { 1, "a" }, { 2, "b" }, { 3, "c" } };
Each item in the braces is simply transformed to the call of Add method with appropriate signature.
var list = new List<int>();
list.Add(1);
list.Add(2);
list.Add(3);
var dic = new Dictionary<int,string>();
dic.Add(1,"a");
dic.Add(2,"b");
dic.Add(3,"c");
It's a bit more complex in reality, but it doesn't matter here.
So, when I first saw description of the feature I thought: How cool! I can specify extension method "Add" for "StringBuilder" and get the following:
var sb = new StringBuilder { "Text = ", Text, ";", "Value = ", Value };
But, restrictions are too strong - type being constructed should implement IEnumerable and have instance method "Add". IEnumerable is not of a big deal, but inability to use extension methods for Add is deal breaker.
How about this?
XmlDocument doc = new XmlDocument
{
new Node("person") { Attributes = { { "name", "John" }, { "age", "42" } },
Nodes =
{
new Node("phones") { Nodes =
{
new Node("number") { Value = "123 45 678" },
new Node("number") { Value = "777 77 777" },
new Node("number") { Value = "987 65 432" }
}
}
}
No way. You can't use collection initializer for XmlDocument, because it doesn't have Add methods. It is IEnumerable, though.
May be this?
var set = new PermissionSet( new ZoneIdentityPermission(...), new PrincipalPermission(...) };
No way. PermissionSet is IEnumerable too, but does have AddPermission instead of Add method.
If it only were searching for candidates as follows:
- If type implements "IEnumerable", look for instance Add method with appropriate parameters,
- If not found, if type implements "IEnumerable", look for extension method Add with appropriate parameters,
- If not found, look for extension method AddToSequence with appropriate parameters.
This change, or something similar, would turn the otherwise very limited collection initializers into really powerfull object initialization feature.
04 September 2007
Visualize Right Margin in Visual Studio
ReSharper has formatting option to keep your source code lines below certain limit.
In Options, go to Languages / C# / Formatting Style / Line Breaks and Wrapping, find "Wrap long lines" below "Line Wrapping" group and enable it, then set "Right margin (columns)" to the desired value. That's pretty cool, but how can one see which lines will be wrapped?
Meet Visual Studio secret feature: Guides!
As described in this blog post, you can play a bit with registry and make Visual Studio display nice dotted vertical lines at specific column:
Now you will be able to see when your lines are too long, and probably make manual formatting before ReSharper will split lines at next reformat.
In Options, go to Languages / C# / Formatting Style / Line Breaks and Wrapping, find "Wrap long lines" below "Line Wrapping" group and enable it, then set "Right margin (columns)" to the desired value. That's pretty cool, but how can one see which lines will be wrapped?
Meet Visual Studio secret feature: Guides!
As described in this blog post, you can play a bit with registry and make Visual Studio display nice dotted vertical lines at specific column:
- Open "HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\9.0\Text Editor" key
- Create new string value "Guides"
- Set its value to something like "RGB(192,192,192) 119" (columns in registry are zero-based)
- Restart Visual Studio
Now you will be able to see when your lines are too long, and probably make manual formatting before ReSharper will split lines at next reformat.
30 August 2007
ReSharper vs C# 3.0 - Implicitly Typed Locals
Last month I was on vacation, living in the country, with no access to Internet, doing no programming, reading non-technical books, walking, swimming and otherwise enjoying my life, my family and the nature. It was really-really cool! However, I admit I was thinking a bit about ReSharper features for C# 3.0 and one of the things that puzzled me was
Obviously, developer have to use var keyword in case of anonymous types, and can't use var if local variable's type cannot be inferred at the declaration point. But most locals are suitable for both forms - explicit type and var keyword. Context action to switch from explicit type to var and back is okay, but we would like to analyse the code and suggest using var in cases where it will improve the code.
Some cases where it seems just fine to suggest var are:
However, various code styles may need to suggest in other cases. For example, programming in functional style with small methods can benefit from suggesting every suitable local variable to be converted to var style. Or may be your project has IElement root interface and you just know that every variable with "element" name is IElement and you don't want explicit types for this case. Probably, any method with the name GetTreeNode() always return ITreeNode and you want vars for all such local variable.
Currently, we have two suggestions: one that suggests every suitable explicitly typed local to be converted to implicityly typed var, and another that suggests according to rules above. They work fine within the team. I hope EAP will give us some feedback about how it works, but Early Access Program for ReSharper 4.0 will be opened later this year.
Meanwhile, do you have any ideas, suggestions or examples where you'd like to see suggestion to convert explicitly typed local variable to the var form?
To var or not to var?
Obviously, developer have to use var keyword in case of anonymous types, and can't use var if local variable's type cannot be inferred at the declaration point. But most locals are suitable for both forms - explicit type and var keyword. Context action to switch from explicit type to var and back is okay, but we would like to analyse the code and suggest using var in cases where it will improve the code.
Some cases where it seems just fine to suggest var are:
- New object creation expression: var dictionary = new Dictionary<int, string>();
- Cast expression: var element = (IElement)obj;
- Safe Cast expression: var element = obj as IElement;
- Generic method call with explicit type arguments, when return type is generic: var manager = serviceProvider.GetService<IManager>()
- Generic static method call or property with explicit type arguments, when return type is generic: var manager = Singleton<Manager>.Instance;
However, various code styles may need to suggest in other cases. For example, programming in functional style with small methods can benefit from suggesting every suitable local variable to be converted to var style. Or may be your project has IElement root interface and you just know that every variable with "element" name is IElement and you don't want explicit types for this case. Probably, any method with the name GetTreeNode() always return ITreeNode and you want vars for all such local variable.
Currently, we have two suggestions: one that suggests every suitable explicitly typed local to be converted to implicityly typed var, and another that suggests according to rules above. They work fine within the team. I hope EAP will give us some feedback about how it works, but Early Access Program for ReSharper 4.0 will be opened later this year.
Meanwhile, do you have any ideas, suggestions or examples where you'd like to see suggestion to convert explicitly typed local variable to the var form?
25 July 2007
ReSharper vs C# 3.0 - Extension Methods
I'm going to do several posts about how are we going to support C# 3.0 in ReSharper. I will not dig into much technical details, instead I will discuss end-user experience and product decisions we have to make. These posts are not meant to be description of features, they are rather invitation to discussion - what do you want to see in ReSharper for C# 3.0.
Today I'm going to discuss Extension Methods.
Note: Information, features and ideas contained in this post are preliminary and subject to change in the release version of ReSharper with C# 3.0 support.
In short, extension methods feature provides ability to pseudo-extend some type's public interface via static member. Compiler looks for static methods marked with System.Runtime.CompilerServices.ExtensionAttribute in the static class with the same attribute. It then converts obj.ExtensionMethod(params) into ExtensionClass.ExtensionMethod(obj, params) while compiling. There is also syntactic sugar to mark methods as extensions - you prefix first parameter of ExtensionMethod with "this" keyword:
As soon as you have instance of List, namespace of ExtensionClass imported into current file and System.Core assembly referenced you can use it as follows:
What does it mean for ReSharper? Well, besides parsing and resolving, it mostly means updating many features to support extension methods, like parameter information, navigation and search.
There will be a number of context actions, analyses and quick fixes to help with extension methods. For example, you already added "this" to the first parameter of the static member, but still using it in the form of a static method in your code, like this: ListExtensions.Process(list,1). In this case suggestion could be issued to convert to the pseudo-instance form: list.Process(1);
There are also some things that should be done specifically for Extension Methods feature. It would be very handy to have completion feature which lists non-imported extensions and insert using directives when you select one, much like Type Name Completion. Most likely we will extend existing feature to work after "dot" and rename it as "Import Name Completion".
It would be nice to have a refactoring to convert existing static member in a static class into extension method and update all usages to the pseudo-instance form.
When implementing interfaces, ReSharper could also look for extension methods that match interface members and current type, and suggest to use them as default implementation instead of throwing NotImplementedException.
If you have any other ideas about supporting Extension Methods in ReSharper, you are welcome to comment on this post.
Today I'm going to discuss Extension Methods.
Note: Information, features and ideas contained in this post are preliminary and subject to change in the release version of ReSharper with C# 3.0 support.
In short, extension methods feature provides ability to pseudo-extend some type's public interface via static member. Compiler looks for static methods marked with System.Runtime.CompilerServices.ExtensionAttribute in the static class with the same attribute. It then converts obj.ExtensionMethod(params) into ExtensionClass.ExtensionMethod(obj, params) while compiling. There is also syntactic sugar to mark methods as extensions - you prefix first parameter of ExtensionMethod with "this" keyword:
public static class ListExtensions
{public static void Process(this List<int> list, int p) {}
}
As soon as you have instance of List
void Foo(List<int> list)
{list.Process(1);
}
What does it mean for ReSharper? Well, besides parsing and resolving, it mostly means updating many features to support extension methods, like parameter information, navigation and search.
There will be a number of context actions, analyses and quick fixes to help with extension methods. For example, you already added "this" to the first parameter of the static member, but still using it in the form of a static method in your code, like this: ListExtensions.Process(list,1). In this case suggestion could be issued to convert to the pseudo-instance form: list.Process(1);
There are also some things that should be done specifically for Extension Methods feature. It would be very handy to have completion feature which lists non-imported extensions and insert using directives when you select one, much like Type Name Completion. Most likely we will extend existing feature to work after "dot" and rename it as "Import Name Completion".
It would be nice to have a refactoring to convert existing static member in a static class into extension method and update all usages to the pseudo-instance form.
When implementing interfaces, ReSharper could also look for extension methods that match interface members and current type, and suggest to use them as default implementation instead of throwing NotImplementedException.
If you have any other ideas about supporting Extension Methods in ReSharper, you are welcome to comment on this post.
23 July 2007
ReSharper 3.0 Screencast Contest
Are you experienced ReSharper user and want to demonstrate the productivity boost you gain with ReSharper?
Do you like it, but cannot afford to pay the cost?
May be you think you are the BEST in using Visual Studio with ReSharper?
Probably, you are evaluating ReSharper 3.0 and have some time to share your experience?
Even if you don't want to compete for free personal license for ReSharper 3.0 Full Edition, you can help us make the most intelligent add-in for Visual Studio even better, smarter and handy. Participate in video contest - show us your coding session!
P.S. If you already spent your 30 days evaluation time, you can download latests ReSharper 3.0.2 EAP builds, which has renewed evaluation period.
Do you like it, but cannot afford to pay the cost?
May be you think you are the BEST in using Visual Studio with ReSharper?
Probably, you are evaluating ReSharper 3.0 and have some time to share your experience?
Even if you don't want to compete for free personal license for ReSharper 3.0 Full Edition, you can help us make the most intelligent add-in for Visual Studio even better, smarter and handy. Participate in video contest - show us your coding session!
P.S. If you already spent your 30 days evaluation time, you can download latests ReSharper 3.0.2 EAP builds, which has renewed evaluation period.
12 July 2007
ReSharper 3.0.2 Early Access Program
We opened ReSharper 3.0.2 Early Access Program and now you can download nightly builds of the next bugfix update for ReSharper 3.0.
What is EAP and why do you want to participate?
There are two major benefits in using early builds and participating in the program:
Why do we need EAP?
We need EAPers for the one simple reason - we can't setup that many test environments people have around the world. Various technologies, libraries, plugins, regional and cultural differences, operation systems and more and more. We can't cover it all. We also can't learn all that styles people do development in. With EAP we can listen to you, and listen early.
How to get most from EAP?
What is EAP and why do you want to participate?
There are two major benefits in using early builds and participating in the program:
- You get the cutting edge technologies, new features, productivity improvements and bug fixes as soon as they are implemented. You don't have to wait for release, you can start working more effective immediately.
- You can influence product development and make sure it works right for you, in your environment, for your development style.
Why do we need EAP?
We need EAPers for the one simple reason - we can't setup that many test environments people have around the world. Various technologies, libraries, plugins, regional and cultural differences, operation systems and more and more. We can't cover it all. We also can't learn all that styles people do development in. With EAP we can listen to you, and listen early.
How to get most from EAP?
- Be proactive. If you see something you don't like - tell us. If you feel something works slow - tell us. If you miss a feature, if you think ReSharper should be smarter in particular case, if you find a typo - file a request in our JIRA database.
- Communicate. It doesn't work in a "fire and forget" style. Don't be anonymous, answer the questions team may ask. Explain why the feature is important and how it should work, give code examples to reproduce a bug, make screenshot when you think you see something wrong.
- Update and share. I know, it takes some time to download and install new build. I wouldn't suggest to update daily, but if you are interested in taking most from EAP you'd update at least weekly. Tell us and other EAPers how the build is going. Discuss improvements and degradations. Share your experience.
- Subscribe to newsgroup or bookmark forums. They are synchronized, so you can use whatever you like most.
- Read about creating requests in our JIRA database. Register in JIRA.
- Download and install ReSharper 3.0.2 nightly build.
Subscribe to:
Posts (Atom)
