💬 Dev Talk: Why Develop CWS?
Status Quo & Pain Points
On most people's computers, Microsoft Office and WPS Office often coexist. Due to the demands of work, school, or specific collaboration needs, it is difficult to completely abandon either one.
However, these two software suites have long been in a "conflict" over system environment ownership:
- File Association Battles: Every time there is an update or an execution, the default opening method for extensions like
.docxor.xlsxis often forcibly modified, disrupting user habits. - Context Menu Redundancy: The right-click "New" menu frequently features duplicate items or displays abnormal icons due to broken associations.
- Residual Background Services: Even after closing the software, conflicting background services continue to consume resources or interfere with the system registry.
Manually fixing these issues is not only tedious (involving numerous registry entries) but also presents a high barrier to entry for non-technical users.
The Positioning of CWS
The development goal of CWS (CleanWS) is crystal clear: to provide a simple, one-click environment repair solution.
It does not attempt to replace any office software, nor does it provide complex management functions. It focuses on three primary tasks:
- Repairing Associations: Restoring file associations to the user's desired state and thoroughly cleaning up incorrect registry indices.
- Cleaning Conflicts: Removing redundant context menu items and resolving logical conflicts caused by residual services.
- Environment Detection: Automatically identifying the current Office/WPS installation environment to prevent repair failures caused by incorrect paths.
Tech Stack & Open Source
- Efficient Framework: Developed using .NET 8 (C#) to ensure native performance and compatibility on the Windows platform.
- Modern UI: Built with WPF (Fluent UI) to keep the tool lightweight while meeting the aesthetic standards of modern operating systems.
- Complete Transparency: CWS is an open-source project. All registry modification logic is public on GitHub, ensuring no irreversible negative impact on the user's system.
Conclusion
The original intention behind CWS was to solve the frustrations I encountered in my daily use. If you are also suffering from Office environment conflicts, I hope this little tool can save you some time spent tinkering with your system.