Last post Jun 14, 2016 09:42 AM by Angie xu - MSFT
Jun 03, 2016 06:04 AM|FJvdM|LINK
We are not sure what is causing this to happen and would appreciate some assistance in resolving this issue.
Thanks in advance.
We suspect that the issue might be caused by source control. That the files that have been worked on and checked in on one machine are not seen as having been changed by the Visual Studio on the machine doing the publication.
Jun 03, 2016 08:50 AM|HostingASPNet|LINK
If the .js files are not excluded from the project all should be updated. The other option is if the .js files are updated on the server, but are in the browser cache, so the user should FLUSH the cache to reload the new files.
Jun 03, 2016 09:28 AM|Angie xu - MSFT|LINK
As you mentioned above, we need expand File Publish Options, and then select
Exclude files from the App_Data folder. It's recommended to deploy the application to IIS on your development computer by using the same process that you'll use later to deploy it to your production environment. See:
Deploying to Test
Have a good day.
Jun 03, 2016 01:06 PM|FJvdM|LINK
All the .js files are included in the project and were published to the server on our first publish.
The other option is if the .js files are updated on the server, but are in the browser cache, so the user should FLUSH the cache to reload the new files.
We checked on the server to verify if the files have been uploaded and only found the old versions, so they weren't updated on the server.
Jun 14, 2016 09:42 AM|Angie xu - MSFT|LINK
You can also try Web One Click Publish.
When you redeploy, Web Deploy automatically determines which files have changed and only copies changed files to the server. By default, Web Deploy uses last-changed dates on files to determine which ones have changed. Some source control systems change
file dates even when you don't change the file contents. In that case, you might want to configure Web Deploy to use file checksums to determine which files have changed.
Deploying a Code Update