tag:blogger.com,1999:blog-3398953.post4796029909650096013..comments2020-11-19T05:21:29.784-08:00Comments on Bloggopottimus: C# NamespacesMarkhttp://www.blogger.com/profile/08999599420983854165noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3398953.post-88590939459455780842010-01-21T22:56:59.693-08:002010-01-21T22:56:59.693-08:00Thanks..this saved me a lot of timeThanks..this saved me a lot of timeAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-3398953.post-51438384895998868342009-06-05T11:02:44.402-07:002009-06-05T11:02:44.402-07:00Thank you for explanations, it really bothered me....Thank you for explanations, it really bothered me. (I bought ReSharper recently and I love it.)Владимирhttps://www.blogger.com/profile/00331194583266302228noreply@blogger.comtag:blogger.com,1999:blog-3398953.post-20796244792678866222007-07-23T12:35:00.000-07:002007-07-23T12:35:00.000-07:00Actually, ReSharper suggests namespace as "Default...Actually, ReSharper suggests namespace as "Default Project Namespace" plus "relative folder path". You can switch the warning altogether in options. You can tune it a bit using properties of the folder in solution explorer - see "Namespace Provider" property. <BR/>Organizing namespaces this way is normal practice in C# world, and VS itself does this way - try to add new class using VS and see default generated namespace. ReSharper's is a bit smarter, though ;)Ilya Ryzhenkovhttps://www.blogger.com/profile/14966746474791511643noreply@blogger.com