IIS changes the physical path to the application.

I have set up two websites in my IIS 8.5. I have one for production and one for development (for team work). The structure is simple. A website is a simple static page that uses BackboneJS and API calls to get all the data. All virtual paths and applications were manually installed. For some reason, some of the API calls didn't work in the dev site. I found out that the physical path to the API project has changed. Do you have any idea where the problem might be? In fact, some of my colleagues are also facing this problem.

Just think that it seems to me that with the bdebugging API I am using the "Attach to process" in Visual Studio where I am attaching to the correct IIS process - w3wp.exe with the username IIS APPPOOL \ Dev or IIS APPPOOL \ Prod according to the site. which I am debugging.

However, I don't think the path should change on its own. Where could the problem be? Does anyone know how to prevent this strange behavior?