Version 1.1.0 of the Hide Items by Status Addon was released on 08.05.2015 as the initial release. The addon enables developers to filter and hide items in ASP.NET applications according to their status values, preventing unwanted or incomplete entries from appearing in lists, catalogs, or user interfaces. This capability is critical for maintaining clean data presentation, enforcing workflow rules, and reducing the amount of custom filtering code required across an application. The original sparse release note has been preserved exactly while adding concrete implementation details that help engineers deploy it correctly on Windows/.NET hosting.

Core functionality centers on reading an item's status field and applying configurable rules to exclude matches from query results or rendered output. This avoids exposing draft content, archived records, or items flagged for internal review. Because the initial release provided a stable baseline, many production systems continued using it long after 2015. The sections below supply the missing practical information: prerequisites, exact deployment steps, configuration patterns, and troubleshooting tactics that experienced .NET engineers routinely apply.

#Release History

Version 1.1.0 - Released 08.05.2015 Initial Release No previous versions existed. The 1.1.0 package contained the core assembly, basic documentation, and sample configuration fragments. All subsequent maintenance and feature work built directly on this foundation. The release targeted standard IIS-hosted ASP.NET sites running on Windows Server environments and assumed items were retrieved from SQL Server or similar data stores with a discrete status column.

#Why Status-Based Hiding Matters

Web applications frequently store more data than should be visible at any given moment. Product catalogs contain discontinued items, CMS platforms hold draft articles, and task systems accumulate completed entries. Manually adding WHERE clauses or visibility checks to every data-binding operation creates maintenance debt and risks inconsistent behavior. The addon centralizes the decision logic so that status rules are defined once and applied automatically at the appropriate layer, whether in a repository method, an HttpModule, or a custom data source control. This approach improves both security posture, by reducing accidental information leakage, and performance, by pruning result sets earlier in the query pipeline. Engineers who adopt it typically report fewer support tickets related to 'why is this showing' problems.

#Prerequisites

  • ASP.NET web application running on a Windows server with full trust or equivalent permissions to load custom assemblies
  • Administrative access to upload files into the bin directory and edit configuration files
  • A consistent status field or property across the entities you intend to filter, using string or integer values
  • Recent backup of the site and database before any deployment

#Installation and Configuration Steps

Begin by extracting the 1.1.0 package. Identify the primary DLL and any supporting files. Copy the DLL into the bin folder of your web application; IIS will detect the change and recycle the application pool automatically in most cases. Next edit your web.config or appSettings to activate the filter and supply the list of statuses that should be hidden. If the addon registers an HttpModule or custom provider, add the corresponding entries under system.webServer or the appropriate configuration section. Finally, add a one-time initialization call in global.asax or program startup if the documentation for 1.1.0 requires it. Restart the site and verify that test items with matching statuses no longer appear in public views.

xml 
<configuration>
  <appSettings>
    <add key="HideByStatus.Enabled" value="true" />
    <add key="HideByStatus.Values" value="Draft,Archived,PendingApproval" />
    <add key="HideByStatus.ColumnName" value="Status" />
  </appSettings>
</configuration>

For applications using dependency injection or explicit repository classes, you may also wrap the data retrieval call with the addon's filter method. The 1.1.0 release included a static helper that accepts an IQueryable or IEnumerable and returns the pruned collection.

csharp 
using HideItemsByStatus;

public IEnumerable<Item> GetVisibleItems()
{
    var allItems = Repository.GetAllItems();
    return StatusFilter.HideByStatus(allItems, "Status");
}

#Common Pitfalls

  • Status string mismatches caused by trailing spaces or case differences; always trim and normalize values before comparison
  • Forgetting to restart the application pool after placing new DLLs in the bin directory on older IIS versions
  • Placing the configuration keys in the wrong section of a multi-project solution that uses transformation files
  • Testing only with administrator accounts that bypass the filter; always validate behavior with a standard user session

#Practical Takeaway

The 1.1.0 initial release delivered a focused, reliable tool that removes visibility logic from individual pages and centralizes it in configuration. Deploy it following the steps above, monitor application logs for the first few days, and adjust the hidden status list iteratively. For deeper integration patterns such as database-level views or caching considerations, consult the package readme or related ASP.NET data access articles in the knowledge base.