You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In case execution of pre-build events for IdP and SP overlap, compilation may intermittently fail. Failure is caused by parallel execution of appcmd processes. Execution of appcmd in IdP races execution of appcmd in SP, leading to "file applicationhost.config locked by other process" compilation error.
In principle, I don't believe there's a need for pre-build events. appcmd setup is only needed once. I suppose the pre-build events were added in order to avoid additional manual steps about first opening the solution in Visual Studio (triggering .vs folder creation), then executing appcmd.
The text was updated successfully, but these errors were encountered:
On second look, I don't believe the precondition added to the pre-build event solves this problem. Two instances of appcmd can still overlap causing intermittent build failure, especially on slower machines.
In case execution of pre-build events for IdP and SP overlap, compilation may intermittently fail. Failure is caused by parallel execution of appcmd processes. Execution of appcmd in IdP races execution of appcmd in SP, leading to "file applicationhost.config locked by other process" compilation error.
In principle, I don't believe there's a need for pre-build events. appcmd setup is only needed once. I suppose the pre-build events were added in order to avoid additional manual steps about first opening the solution in Visual Studio (triggering .vs folder creation), then executing appcmd.
The text was updated successfully, but these errors were encountered: