Skip to content

Commit f4577f1

Browse files
committed
Add note on GitHub Copilot App Modernization for Java and .NET in legacy code guide
1 parent c5e12ee commit f4577f1

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

blog/2025-10-21-modernizing-legacy-code-with-github-copilot-a-documentation-first-approach.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ You can find a video -in French- walkthrough of this approach here:
1919

2020
The key mistake many make is jumping straight from legacy code (like Progress Software in my example) and asking Copilot to "write me a Java app" or "convert this to TypeScript." Instead, the proper approach is to **start with documentation**. We need to begin by creating reverse documentation from the existing code, which then serves as a solid foundation for rewriting. This ensures all functionality is well-documented and provides the right context for generating new code.
2121

22+
If you’re dealing with older Java or .NET applications, the [GitHub Copilot App Modernization](https://github.blog/changelog/2025-09-22-github-copilot-app-modernization-is-now-generally-available-for-java-and-net/) extensions can also assist you. This article focuses on other legacy technologies, but the principle remains the same — Copilot can be a great ally for **retro-documenting** your projects.
23+
2224
You can see a complete example of this retro-documentation process applied to the [Sports App](https://github.com/tug-on-dev/progress-sports-app/tree/main/documentation). _(Originally in French then translated to English using Copilot)_
2325

2426
<!-- truncate -->

0 commit comments

Comments
 (0)