Bugs for AWS transform

**Describe the bug**

**To Reproduce**

**Expected behavior**

**Screenshots**

**Toolkit Logs**

**Development System (please complete the following information):**
- Windows Version:
- Visual Studio Version:
- AWS Toolkit for Visual Studio Version:

**Additional context**

What doesn’t work well:

1. ASMX services are not supported

ASMX web services are skipped entirely.

No Program.cs, routing, or SOAP host is generated.

The migrated project is not runnable without major manual effort.

2. Referenced DLLs are not handled properly

The tool cannot read logic from compiled assemblies.

It inserts unsafe reflection-based code in place of actual method calls.

This leads to broken functionality and unreadable, unmaintainable output.

3. Performance issues with large or DLL-heavy projects

Transformation takes hours for moderately sized solutions.

Some projects hang or skip files; retries may be needed multiple times.

In some cases, clearing cache and history was required to proceed.

4. No functional code refactoring or cleanup

Code structure remains legacy-oriented.

No modern patterns or cleanup are applied—just framework upgrades.

5. In-house NuGet feeds (e.g., JFrog) are not supported

Custom/internal packages are not recognized or replaced.

Developers must manually rewire dependencies across projects.

6. Unreliable transformation history/logs

Failed jobs don’t always leave logs behind for debugging.

It becomes hard to trace why a job failed or what was skipped.

Start by reproducing each reported transformation problem with a project containing ASMX, referenced DLLs, and an in-house NuGet feed, while collecting Toolkit Logs and recording the Windows, Visual Studio, and toolkit versions. Done means each failure has a reproducible case and a verified resolution or documented limitation, including transformation duration, skipped files, and history/log behavior.

Written by the indexing model from the issue text.