DotNet core (.Net6) winform application with self container takes a lot of time to load on Network FIle share

Sunny Sharma 1 Reputation point
2022-07-13T14:26:30.16+00:00

Hi,
We are developing a winform application on DotNetcore 6. It seems to be working fine locally and on windows machine
using framework dependent deployment as well as self containerized deployment.

The problem occurs with self contained package deployed on network file share (DFS) server which has all the necessary assemblies and runtime along with source code. It takes a lot of time to load. We have even tried using the test application built on DotNetcore 6 Winform with no source even that takes lot of time with self contained deployment package to load. Is there a limitation that application packages using self contained deployment package takes a huge amout of time on network file share and they are not fit to be hosted on network file share? The same packages works fine on other windows server other than the network file share. Have anyone encountered this issue?

.NET
.NET
Microsoft Technologies based on the .NET software framework.
3,356 questions
ASP.NET Core
ASP.NET Core
A set of technologies in the .NET Framework for building web applications and XML web services.
4,148 questions
.NET Runtime
.NET Runtime
.NET: Microsoft Technologies based on the .NET software framework.Runtime: An environment required to run apps that aren't compiled to machine language.
1,118 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Bruce (SqlWork.com) 55,196 Reputation points
    2022-07-13T20:51:15.65+00:00

    the first time a self contained exe is run, it extracts all the files to a folder created in temp (%LOCALAPPDATA%\Temp.net{nameofexe}). this extraction is slower over a network. also this extraction may trigger virus scans if enabled.

    if the temp folder is deleted or out of date, then the extraction must be done again.

    note: this is windows only, macOs has application bundle support builtin.