<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Software Quality Blog &#8211; SubMain Software</title>
	<atom:link href="https://blog.submain.com/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.submain.com</link>
	<description>Code Quality Tools, Automated Code Review and Refactoring</description>
	<lastBuildDate>Mon, 07 Feb 2022 20:12:59 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://i0.wp.com/blog.submain.com/wp-content/uploads/2018/11/cropped-CodeItRight_Qualimark_702x702.fw_.png?fit=32%2C32&#038;ssl=1</url>
	<title>Software Quality Blog &#8211; SubMain Software</title>
	<link>https://blog.submain.com</link>
	<width>32</width>
	<height>32</height>
</image> 
<site xmlns="com-wordpress:feed-additions:1">130870859</site>	<item>
		<title>CodeIt.Right for VS2022</title>
		<link>https://blog.submain.com/codeit-right-for-vs2022/</link>
					<comments>https://blog.submain.com/codeit-right-for-vs2022/#respond</comments>
		
		<dc:creator><![CDATA[Serge Baranovsky]]></dc:creator>
		<pubDate>Mon, 06 Dec 2021 22:53:02 +0000</pubDate>
				<category><![CDATA[CodeIt.Right]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Releases]]></category>
		<guid isPermaLink="false">https://blog.submain.com/?p=1138</guid>

					<description><![CDATA[CodeIt.Right v2022 is now available! Added Visual Studio 2022 integration Added x64 development environment support Visual Studio is 64-bit The most exciting news about Visual Studio 2022 is that it will be 64-bit. This is a giant leap forward as far as the memory available to the Visual Studio environment! Due to the existing Visual Studio being a 32-bit process, it can only use a maximum of 4 GB of memory. That memory is shared between the project files, the runtime, the extensions, and the VS environment itself. So regardless of how powerful your development rig is, current Visual Studio can only use some 4GB of memory, even if you got 32GB available. VS2022 being x64 is excellent news! Especially if you have large solutions! What does this mean for CodeIt.Right? Since both CodeIt.Right is a Visual Studio extension and exists within that VS environment&#8217;s memory space, both will be...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/codeit-right-for-vs2022/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1138</post-id>	</item>
		<item>
		<title>VS2022 Readiness Update</title>
		<link>https://blog.submain.com/vs2022-readiness-update/</link>
					<comments>https://blog.submain.com/vs2022-readiness-update/#comments</comments>
		
		<dc:creator><![CDATA[Serge Baranovsky]]></dc:creator>
		<pubDate>Thu, 08 Jul 2021 01:56:44 +0000</pubDate>
				<category><![CDATA[Beta]]></category>
		<category><![CDATA[CodeIt.Right]]></category>
		<category><![CDATA[GhostDoc]]></category>
		<category><![CDATA[News]]></category>
		<guid isPermaLink="false">https://blog.submain.com/?p=1121</guid>

					<description><![CDATA[If you are reading this post, you already know that Microsoft has announced a new version of Visual Studio 2022. And of course, we make sure that our products are available to help you improve your code and code documentation. TLDR; We already have a version of GhostDoc Pro, GhostDoc Enterprise, and CodeIt.Right, that is compatible with Visual Studio 2022 Preview. If you are interested in trying these out, see the details at the end of this post. Visual Studio is 64-bit The most exciting news about Visual Studio 2022 is that it will be 64-bit. This is a giant leap forward as far as the memory available to the Visual Studio environment! Due to the existing Visual Studio being a 32-bit process, it can only use a maximum of 4 GB of memory. That memory is shared between the project files, the runtime, the extensions, and the VS environment...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/vs2022-readiness-update/feed/</wfw:commentRss>
			<slash:comments>8</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1121</post-id>	</item>
		<item>
		<title>Released: GhostDoc v2021</title>
		<link>https://blog.submain.com/released-ghostdoc-v2021/</link>
					<comments>https://blog.submain.com/released-ghostdoc-v2021/#respond</comments>
		
		<dc:creator><![CDATA[Serge Baranovsky]]></dc:creator>
		<pubDate>Tue, 15 Dec 2020 19:11:24 +0000</pubDate>
				<category><![CDATA[GhostDoc]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Releases]]></category>
		<guid isPermaLink="false">https://blog.submain.com/?p=1096</guid>

					<description><![CDATA[Note to the GhostDoc v2020 users: The v2021 requires a new license code. Users with License Protection or active Software Assurance subscription are eligible for a free upgrade. See the information at the bottom of this post for the details. Now with TypeScript support We added support for TypeScript language and TypeScript projects Currently supported in Document This Re-document This Document Type Document File Document Project Not supported yet in Document File Header Document Checked Out Files Exclude This from Documentation Visual Comment Editor Generate Help Documentation Preview Comment Documentation Maintenance Dark Theme for help documentation In addition to the FlatGray and FlatMain themes, GhostDoc is now offering the new DarkMain theme. Other changes Backup error-recovery compliant parsing engine that improves the quality of comment template generation in Document This/Type/File/Project, Comment Preview, and Build Help Documentation Display subscription information in the About window No longer distributing the legacy frame-based themes...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/released-ghostdoc-v2021/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1096</post-id>	</item>
		<item>
		<title>Released: GhostDoc v2020</title>
		<link>https://blog.submain.com/released-ghostdoc-v2020/</link>
					<comments>https://blog.submain.com/released-ghostdoc-v2020/#respond</comments>
		
		<dc:creator><![CDATA[Serge Baranovsky]]></dc:creator>
		<pubDate>Fri, 13 Mar 2020 06:51:16 +0000</pubDate>
				<category><![CDATA[GhostDoc]]></category>
		<category><![CDATA[News]]></category>
		<category><![CDATA[Releases]]></category>
		<guid isPermaLink="false">https://blog.submain.com/?p=1047</guid>

					<description><![CDATA[If are you are a licensed user with a current subscription, you can retrieve your permanent v2020 license code using the MyAccount page. The new major version of GhostDoc, v2020, is now available for download. Changes in v2020 New and improved syntax editor for Rule Template editor and Visual Editor New menu batch action &#8211; &#8216;Document Checked Out Files&#8217; Documentation Maintenance &#8211; now allow analysis on Solution/Project level for &#8216;Missing Documentation&#8217;, &#8216;Auto-generated Documentation&#8217;, &#8216;Synchronize with member signature&#8217; Documentation Maintenance &#8211; improved responsiveness and performance when running the maintenance analysis on a large number of files or projects. New Re-Document action in the Visual Editor Visual Editor improvements &#8211; &#60;see&#62; and &#60;seealso&#62; authoring support, key combination Ctrl+Enter now saves and close the window Rule Template editor &#8211; easier template customization with improved Intellisense, added Quick Info (on mouseover), Completion List (Ctrl+Space), and Parameter Info (EE) New x64 command-line utility allows producing...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/released-ghostdoc-v2020/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1047</post-id>	</item>
		<item>
		<title>Visual Studio Extensions: 7 You Should Check Out</title>
		<link>https://blog.submain.com/visual-studio-extensions-7-you-should-check-out/</link>
					<comments>https://blog.submain.com/visual-studio-extensions-7-you-should-check-out/#respond</comments>
		
		<dc:creator><![CDATA[Carlos Schults]]></dc:creator>
		<pubDate>Tue, 26 Nov 2019 13:44:30 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[CarlosSchults]]></category>
		<guid isPermaLink="false">https://blog.submain.com/?p=1025</guid>

					<description><![CDATA[If you&#8217;ve been a .NET developer for any reasonable amount of time, then you&#8217;re surely aware of what Visual Studio extensions are. If you haven&#8217;t, well, they&#8217;re pretty much what it says in the name: pieces of software (plugins, if you will) that you can add to your Visual Studio IDE to extend its capabilities. Today&#8217;s post features a list of eight extensions that we believe are worth your time. By the end of the article, you&#8217;ll have a good grasp of the available extensions out there, and will potentially adopt some of them to make your life easier. Let&#8217;s get started. 1. AxoCover We open our list with AxoCover, which is a free code coverage extension for Visual Studio. AxoCover allows you to efficiently run and debug your tests, as well as organizing them hierarchically. And of course, it analyzes and displays the coverage for your code at the...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/visual-studio-extensions-7-you-should-check-out/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1025</post-id>	</item>
		<item>
		<title>C# Select and Where: Writing SQL-Style Queries in Code</title>
		<link>https://blog.submain.com/c-select-where-writing-sql-style-queries/</link>
					<comments>https://blog.submain.com/c-select-where-writing-sql-style-queries/#respond</comments>
		
		<dc:creator><![CDATA[Eric Boersma]]></dc:creator>
		<pubDate>Tue, 12 Nov 2019 14:06:23 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[CodeBasics]]></category>
		<category><![CDATA[EricBoersma]]></category>
		<guid isPermaLink="false">https://blog.submain.com/?p=1006</guid>

					<description><![CDATA[C# is a marvelous language. It&#8217;s powerful, fast, and easy to learn. It also exposes advanced features that make doing otherwise difficult things simple. Even more impressively, it manages to make reading the code to do those complicated things easy, too. Many programming languages struggle with this last part. You might be able to do something really cool, but the code is opaque for other developers to read. One example of a feature where C# makes the difficult easy is in the Language Integrated Natural Query (LINQ) interface. If you&#8217;ve been working with a C# code base for a little while, you might have run up against some LINQ code. The first time you see it can feel a little confusing. Some variations of LINQ code look like an entirely different programming language from the C# that you&#8217;re used to. Even for variations of LINQ that aren&#8217;t entirely different syntax,...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/c-select-where-writing-sql-style-queries/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">1006</post-id>	</item>
		<item>
		<title>Code Cleanup: 7 Simple Daily Steps That Pay off in the End</title>
		<link>https://blog.submain.com/code-cleanup-7-simple-daily-steps-that-pay-off-in-the-end/</link>
					<comments>https://blog.submain.com/code-cleanup-7-simple-daily-steps-that-pay-off-in-the-end/#comments</comments>
		
		<dc:creator><![CDATA[Carlos Schults]]></dc:creator>
		<pubDate>Tue, 29 Oct 2019 14:01:47 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[CarlosSchults]]></category>
		<category><![CDATA[CodeIt.Right]]></category>
		<category><![CDATA[LegacyCode]]></category>
		<category><![CDATA[TechnicalDebt]]></category>
		<guid isPermaLink="false">http://blog.submain.com/?p=994</guid>

					<description><![CDATA[&#8220;Code cleanup&#8221; is a phrase that sounds like it&#8217;s a lot of work. Well, sometimes it may be an arduous task, indeed. But that doesn&#8217;t mean it&#8217;s the way it should be. As with many things in software development—and in general life—it&#8217;s often more comfortable, less painful and more productive to do an unpleasant task every day, little by little than let it accumulate and become a monster. That&#8217;s what today&#8217;s post is about. We&#8217;ll present seven simple code cleanup tasks that you can perform daily, to keep your codebase readable, easy to navigate, and maintain. We don&#8217;t necessarily expect you to perform all of the steps every day. On some days, you might be able to pull it off, but on others, it might be harder to do so. Think of the seven tips you&#8217;ll read as a practical embodiment of the scouting principle: leave the code better than...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/code-cleanup-7-simple-daily-steps-that-pay-off-in-the-end/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">994</post-id>	</item>
		<item>
		<title>C# Documentation: A Start to Finish Guide</title>
		<link>https://blog.submain.com/c-documentation-start-finish-guide/</link>
					<comments>https://blog.submain.com/c-documentation-start-finish-guide/#comments</comments>
		
		<dc:creator><![CDATA[Carlos Schults]]></dc:creator>
		<pubDate>Tue, 15 Oct 2019 13:28:11 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[CarlosSchults]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[GhostDoc]]></category>
		<guid isPermaLink="false">http://blog.submain.com/?p=977</guid>

					<description><![CDATA[If you&#8217;re a regular reader of this blog, you&#8217;ll know that code documentation is a topic we tend to cover with a certain frequency. Another common topic is concepts related to the C# language. In today&#8217;s post, we make these two common subjects converge, by presenting a guide on C# documentation. We&#8217;ll show you a step-by-step guide that will walk you through the necessary steps you need to take to create documentation for your C# code. You&#8217;ll start by adding documentation to your code using special XML comments and end by seeing how to generate rich documentation created from these comments. You&#8217;ll learn about the importance of code documentation, see how Visual Studio can turn the documentation you create into useful help messages, and get to know some tools that can help you in this work. Let&#8217;s get started! Code Documentation: Why Bother? We begin by explaining the motivations behind...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/c-documentation-start-finish-guide/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">977</post-id>	</item>
		<item>
		<title>C# Inheritance: A Complete but Gentle Introduction</title>
		<link>https://blog.submain.com/c-inheritance-complete-introduction/</link>
					<comments>https://blog.submain.com/c-inheritance-complete-introduction/#comments</comments>
		
		<dc:creator><![CDATA[Carlos Schults]]></dc:creator>
		<pubDate>Tue, 01 Oct 2019 13:22:42 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[CarlosSchults]]></category>
		<category><![CDATA[CodeBasics]]></category>
		<guid isPermaLink="false">http://blog.submain.com/?p=969</guid>

					<description><![CDATA[Time for another dive into a concept of the C# language. Today&#8217;s post will cover inheritance, a concept that will make us analyze the object-oriented side of C#. As the title of the article makes clear, this post is a gentle introduction to the concept of inheritance. It&#8217;s aimed at beginners that still haven&#8217;t mastered inheritance. That means that, despite being a complete introduction, we&#8217;ll not venture into more advanced aspects of the concept. By the end of the post, you&#8217;ll not know everything there is to know about C# inheritance. Instead, you&#8217;ll have a solid working knowledge, upon which you can keep building more and more. Let&#8217;s get started. Defining C# Inheritance Inheritance is a feature present in object-oriented languages, and it&#8217;s one of the most essentials features at that. It&#8217;s not rare to see people describing it as a mechanism to help you achieve code reuse. Sure, inheritance...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/c-inheritance-complete-introduction/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">969</post-id>	</item>
		<item>
		<title>Building a Pragmatic, Lightweight Code Review Checklist</title>
		<link>https://blog.submain.com/building-code-review-checklist/</link>
					<comments>https://blog.submain.com/building-code-review-checklist/#comments</comments>
		
		<dc:creator><![CDATA[Eric Boersma]]></dc:creator>
		<pubDate>Tue, 17 Sep 2019 13:57:44 +0000</pubDate>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[CodeIt.Right]]></category>
		<category><![CDATA[CodeReviews]]></category>
		<category><![CDATA[EricBoersma]]></category>
		<guid isPermaLink="false">http://blog.submain.com/?p=963</guid>

					<description><![CDATA[A good code review can feel like magic. A skilled code reviewer will deftly work through each part of a pull request, noting potential problems and proposing elegant solutions. If you&#8217;re like many developers, you recognize a good code review when you see one. You&#8217;ve probably even created a few yourself. But you&#8217;re probably also a bit unsure as to how to make sure that your code reviews are good every time. One way to improve your code reviews consistently is to create a code review checklist that you run through every time you review code. A checklist makes sure that you don&#8217;t forget anything. At the same time, that checklist will stop you from turning the code review into a giant slog. You don&#8217;t want a simple code review to take hours, but you also don&#8217;t want to be the person who approves sketchy code, either. In this article,...]]></description>
		
					<wfw:commentRss>https://blog.submain.com/building-code-review-checklist/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
		<post-id xmlns="com-wordpress:feed-additions:1">963</post-id>	</item>
	</channel>
</rss>
