<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/">
  <channel>
    <language>en_US</language>
    <title>Text Control Blog Feed - CI only</title>
    <description>The Text Control Blog is the central information channel for all Text Control products. We post news updates, product information, sample applications, technical articles, tutorials and conference reports several times a week. Subscribe to the feed today.</description>
    <image>
      <url>https://s1-www.textcontrol.com/assets/dist/img/favicon/favicon-128x128.png</url>
      <title>Text Control Blog Feed - CI only</title>
      <link>https://www.textcontrol.com/blog/tag/ci/2024/</link>
    </image>
    <pubDate>Tue, 03 Mar 2026 10:20:03 +0000</pubDate>
    <lastBuildDate>Tue, 03 Mar 2026 10:20:03 +0000</lastBuildDate>
    <generator>Text Control Feed Generator 3.0</generator>
    <link>https://www.textcontrol.com/blog/tag/ci/2024/</link>
    <copyright>Text Control</copyright>
    <atom:link rel="self" type="application/rss+xml" href="https://www.textcontrol.com/feed/blog/tag/ci.xml"/>
    <item>
      <title>Azure Pipelines with TX Text Control .NET for ASP.NET 32.0 with Azure DevOps and Artifacts</title>
      <description><![CDATA[Continuous integration is a common practice in which code is compiled on build servers at regular intervals for testing after commit or at specific stages of development. This article shows how to use TX Text Control .NET Server 32.0 in such environments, and in particular how to handle licensing.]]></description>
      <pubDate>Fri, 05 Jan 2024 11:00:00 +0000</pubDate>
      <link>https://www.textcontrol.com/blog/2024/01/05/azure-pipelines-with-tx-text-control-net-for-asp-net-32-0-with-azure-devops-and-artifacts/</link>
      <guid isPermaLink="false">10012814-50a7-5df7-9897-9ff97bc4a4ee</guid>
      <author>no-reply@textcontrol.com (Bjoern Meyer)</author>
      <enclosure type="image/jpeg" length="42427" url="https://s1-www.textcontrol.com/assets/dist/blog/2024/01/05/c/assets/thumbnail.jpg"/>
      <category domain="https://www.textcontrol.com/blog/tag/aspnet/2024/"><![CDATA[ASP.NET]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/azure-devops/2024/"><![CDATA[Azure DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/ci/2024/"><![CDATA[CI]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/devops/2024/"><![CDATA[DevOps]]></category>
      <dc:creator>Bjoern Meyer</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Azure Pipelines with TX Text Control .NET for WPF and Windows Forms 32.0 with Azure DevOps and Artifacts</title>
      <description><![CDATA[Continuous integration is a common practice of periodically compiling code on build servers to run tests after commits or at certain stages of development. This article shows how to use TX Text Control .NET for WPF and Windows Forms in such environments, and in particular how to handle licensing.]]></description>
      <pubDate>Fri, 05 Jan 2024 11:00:00 +0000</pubDate>
      <link>https://www.textcontrol.com/blog/2024/01/05/azure-pipelines-with-tx-text-control-net-for-wpf-and-windows-forms-320-with-azure-devops-and-artifacts/</link>
      <guid isPermaLink="false">0ac86c71-19f4-5dcb-82f4-31e93e15d5db</guid>
      <author>no-reply@textcontrol.com (Bjoern Meyer)</author>
      <enclosure type="image/jpeg" length="42427" url="https://s1-www.textcontrol.com/assets/dist/blog/2024/01/05/b/assets/thumbnail.jpg"/>
      <category domain="https://www.textcontrol.com/blog/tag/azure-devops/2024/"><![CDATA[Azure DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/ci/2024/"><![CDATA[CI]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/devops/2024/"><![CDATA[DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/windows-forms/2024/"><![CDATA[Windows Forms]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/wpf/2024/"><![CDATA[WPF]]></category>
      <dc:creator>Bjoern Meyer</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Azure Pipelines with TX Text Control .NET for WPF and Windows Forms 31.0 with Azure DevOps and Artifacts</title>
      <description><![CDATA[Continuous integration is a common practice of periodically compiling code on build servers to run tests after commits or at certain stages of development. This article shows how to use TX Text Control .NET for WPF and Windows Forms in such environments, and in particular how to handle licensing.]]></description>
      <pubDate>Fri, 12 May 2023 10:00:00 +0000</pubDate>
      <link>https://www.textcontrol.com/blog/2023/05/12/azure-pipelines-with-tx-text-control-net-for-wpf-and-windows-forms-310-with-azure-devops-and-artifacts/</link>
      <guid isPermaLink="false">dd587c03-f0ce-5246-a356-f3838c99d142</guid>
      <author>no-reply@textcontrol.com (Bjoern Meyer)</author>
      <enclosure type="image/jpeg" length="40178" url="https://s1-www.textcontrol.com/assets/dist/blog/2023/05/12/a/assets/thumbnail.jpg"/>
      <category domain="https://www.textcontrol.com/blog/tag/azure-devops/2023/"><![CDATA[Azure DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/ci/2023/"><![CDATA[CI]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/devops/2023/"><![CDATA[DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/windows-forms/2023/"><![CDATA[Windows Forms]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/wpf/2023/"><![CDATA[WPF]]></category>
      <dc:creator>Bjoern Meyer</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Compiling TX Text Control .NET Server 31.0 with Azure DevOps and Artifacts</title>
      <description><![CDATA[Continuous Integration is a common practice to compile code on build servers periodically to run tests after commits or at specific development stages. This article shows how to use TX Text Control within such environments and in specific how to handle the licensing.]]></description>
      <pubDate>Mon, 24 Oct 2022 10:00:00 +0000</pubDate>
      <link>https://www.textcontrol.com/blog/2022/10/24/using-tx-text-control-with-build-servers/</link>
      <guid isPermaLink="false">89cf9c12-727a-5112-9360-e6db00edc343</guid>
      <author>no-reply@textcontrol.com (Bjoern Meyer)</author>
      <enclosure type="image/jpeg" length="55772" url="https://s1-www.textcontrol.com/assets/dist/blog/2022/10/24/a/assets/thumbnail.jpg"/>
      <category domain="https://www.textcontrol.com/blog/tag/aspnet/2022/"><![CDATA[ASP.NET]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/azure-devops/2022/"><![CDATA[Azure DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/ci/2022/"><![CDATA[CI]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/devops/2022/"><![CDATA[DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/windows-forms/2022/"><![CDATA[Windows Forms]]></category>
      <dc:creator>Bjoern Meyer</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Preparing Projects for GitHub Actions</title>
      <description><![CDATA[Software workflow automation allows an ongoing and continuous monitoring throughout the development, code review, branch management and deployment of software projects. This article shows how to prepare a project for GitHub Actions that uses TX Text Control.]]></description>
      <pubDate>Mon, 27 Jun 2022 10:00:00 +0000</pubDate>
      <link>https://www.textcontrol.com/blog/2022/06/27/preparing-projects-for-github-actions/</link>
      <guid isPermaLink="false">f49af344-d29e-56a3-9bae-e3d081ae330a</guid>
      <author>no-reply@textcontrol.com (Bjoern Meyer)</author>
      <enclosure type="image/jpeg" length="76346" url="https://s1-www.textcontrol.com/assets/dist/blog/2022/06/27/a/assets/thumbnail.jpg"/>
      <category domain="https://www.textcontrol.com/blog/tag/aspnet/2022/"><![CDATA[ASP.NET]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/ci/2022/"><![CDATA[CI]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/github/2022/"><![CDATA[GitHub]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/github-actions/2022/"><![CDATA[GitHub Actions]]></category>
      <dc:creator>Bjoern Meyer</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
    <item>
      <title>Using TX Text Control .NET Server with Build Servers for Continuous Integration (Azure DevOps)</title>
      <description><![CDATA[Continuous Integration is a common practice to compile code on build servers periodically to run tests after commits or at specific development stages. This article shows how to use TX Text Control within such environments and in specific how to handle the licensing.]]></description>
      <pubDate>Thu, 21 Oct 2021 10:00:00 +0000</pubDate>
      <link>https://www.textcontrol.com/blog/2021/10/21/using-tx-text-control-with-build-servers/</link>
      <guid isPermaLink="false">d69e4970-c473-50b9-870c-93e4f9a36592</guid>
      <author>no-reply@textcontrol.com (Bjoern Meyer)</author>
      <enclosure type="image/jpeg" length="55772" url="https://s1-www.textcontrol.com/assets/dist/blog/2021/10/21/a/assets/thumbnail.jpg"/>
      <category domain="https://www.textcontrol.com/blog/tag/aspnet/2021/"><![CDATA[ASP.NET]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/azure-devops/2021/"><![CDATA[Azure DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/ci/2021/"><![CDATA[CI]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/devops/2021/"><![CDATA[DevOps]]></category>
      <category domain="https://www.textcontrol.com/blog/tag/windows-forms/2021/"><![CDATA[Windows Forms]]></category>
      <dc:creator>Bjoern Meyer</dc:creator>
      <slash:comments>0</slash:comments>
    </item>
  </channel>
</rss>
