<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.dotnetzone.gr:443/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Const vs. readonly vs. static readonly in C# .NET</title><link>https://www.dotnetzone.gr:443/cs/blogs/birbilis/archive/2008/11/23/const-vs-readonly-vs-static-readonly-in-c-net.aspx</link><description>This article by Rinat Abdullin clarifies const vs. readonly vs. static readonly in C# .NET . And as the author says: A class that has only constant or readonly instance fields is considered to be prepared for the concurrency challenges of parallel computing,</description><dc:language>el</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator></channel></rss>