The ClickOnce deployment updated all files except one library on some of the
machines. Anyone have an idea how this could happen?
Details:
Some of our users on slower network connections experienced problems with
the application. Looking at the Local Settings\Apps directories on their
machines showed that one of the dll files was an old version. Everyone else
in the company using the same ClickOnce location got the recent dll.
Checking the IIS install location the filename.dll.deploy file was the
correct version.
The file is set to “Include” in the project publish. The
filename.XmlSerializers.dll is included in the published directory and is
also the old version of course.
|
Similar Threads
