如何删除“加密内容以保护数据”
我的网站在加载从“Superfish”下载的图像、CSS 文件和 JavaScript 文件时出现问题。
我发现问题出在每个文件上的“加密内容以保护数据”。 好的，所以我右键单击->属性->高级且未选中“加密内容以保护数据”设置。
但是，当我使用 Visual Studio 2010 重新发布时，已发布的文件会再次标记该设置。源文件没有设置标志，只有发布的文件。在开始发布之前所有文件都会被删除。
我已经通过将内容粘贴到新文件中来完全重新创建了每个文件，但当它们被复制时，标志仍然被重置。
我尝试发布到另一个文件夹，但遗憾的是，新文件仍然是使用加密内容设置创建的。
似乎 Visual Studio 仍然认为应该标记此设置，或者它正在从未删除该设置的位置复制文件的缓存版本。
如何阻止设置在每次发布后重新标记？
My website had problems loading an image, css file and a javascript file downloaded as a package from "Superfish".
I found the problem to be the "encrypt contents to secure data" on each of the files.
Ok, so I right-click -> properties -> Advanced and unchecked the "encrypt contents to secure data" setting.
However, when I re-publish using Visual Studio 2010, the published files have the setting flagged again. The source files do not have the flag set, only the published files. All files are deleted prior to commencing the publish.
I have completely re-created each file by pasting the contents in to a new file, but still when they are copied across the flag is reset.
I have tried publishing to another folder, but alas the new file still get created with encrypted contents setting.
It seems as though Visual Studio still thinks that this setting should be flagged, or it is copying a cached version of the file from somewhere which hasn't had the setting removed.
How do I stop the setting from being re-flagged after each publish?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我对 CSS 文件也有同样的问题。该文件在项目文件夹内以某种方式加密，因此在部署时，它会继承该标志。将其修复在项目文件夹中解决了问题。
检查您的本地源，确保它没有首先加密。我知道你说不是，但请再检查一下。
I had this same issue with a CSS file. The file was somehow encrypted inside the project folder, so when deployed, it was carrying over that flag. Fixing it in the project folder solved the issue.
Check your local source, make sure it's not encrypted there first. I know you said they weren't, but check again.
我刚刚遇到了完全相同的问题。源文件最初在我的图像文件夹中加密。我在源文件夹中对它们进行了解密，但即使在目标文件夹中删除它们后，发布也会重置目标文件中的加密标志。然而，在完全重建我的解决方案后，问题就消失了。
I just had the exact same issue. The source files were initially encrypted in my images folder. I unencrypted them in the source folder, but even after deleting them in the destination folder, publishing reset the encrypted flag in the destination files. However, after doing a complete rebuild of my solution, the problem went away.