New answers tagged solution-deployment
Finally, I found an another solution for this critical problem. Cause we modified directly js or CSS or some files of Front End in the server SharePoint, "IIS" will keep the original files as web content cache, even we did Ctrl+F5 or empty the cache in browser, that doesn't work at all. I tested many times in that way. So we need Expire the web content in ...
I did the same thing too, and the result is the disaster... However one solution is adding "?Rev=2" after the link of your js. I hope this could help you.
I had to do a combination of things to get this working, and I'm still not confident in Visual Studio for the deploy process. This link showed a known issue with Visual Studio building SharePoint solutions where sometimes the old code (which is no longer in any source files) still gets used during the build process. The only way I could reliably get a full ...
Got the solution Open the file "wss.xsd" at below path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\XML" Find all xs:anyAttribute namespace="##other" processContents="lax" in the file and verify that it is the last child if not move it to the last position . see below piece of code. <xs:attribute name="PrependId" ...
Top 50 recent answers are included