Optimizing WPF Application Startup Time on Shared Network Drive

Question

My team is facing an issue when publishing the application on a shared network drive. When an end user opens the program for the first time after starting their computer, it takes significantly longer compared to running it from the local C drive (18 seconds on the shared network drive vs. 3 seconds on the C drive). Are there any tools or techniques to reduce the file size or optimize the WPF program to make it open faster?

Answer 1

if you are using click once deployment, then the application must be copied to the local computer to run when first run.

Answer 2

Hi, @Knot. Welcome to Microsoft Q&A. 

You could refer to the following optimization solutions:

1. The IO and network reading speeds are too slow, and the initialization program needs to load too many modules (.dll files). Could these modules be loaded dynamically after the program starts? Or preload commonly used dependent libraries and resource files when the program starts, and cache them locally to reduce the dependence on the network during operation.
2. Could the initialization logic (for example: data loading) be executed after the program starts, or asynchronously executed.
3. Segmented loading: Divide large resource files into multiple small files and load them on demand to avoid transmitting large amounts of data at one time.
4. Could a startup screen be added to optimize the user experience

 

More optimization solutions: Application Startup Time - WPF .NET Framework | Microsoft Learn

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.