Anyone, I have deployed a solution that contains content types, managed metadata, new page templates and some written in GAC and etc. I need to change certain features and my landing page references requires changes. After removing the site collection, retracting the solution and removing the solution from the farm, and then redeploy the new changes the old page is still cached. I've used the Remove-SPSite -Identity "<URL>" -GradualDelete Remove-SPSolution When I do a search on my folders I can still find landing.aspx_1717798170.compiled How do I completely delete clean everything from IIS? M Sariman RKO Business Solutions Inc.

I hope you are doing and IIS reset before retracting and removing the solution. Sometimes, we tend to miss IIS reset, that causes the solution removal to be incomplete.Thanks Arut

I did that but I can still see some files lying around. I was hoping if anyone can tell me how to completely cleanup the system when removing a solution and a site. M Sariman RKO Business Solutions Inc.

I guess all the solution and site related files should be ideally removed if you perform the retraction/ removal in the order mentioned below: IIS reset -> Feature Deactivation -> Solution Retraction -> Solution Removal -> Site Removal/ Deletion If not, then you can manually delete them from the 14 hive folders, under inetpub/wwwroot/wss/yoursiteport# folder or cached locations. Most of your solution files must be present in the 14 hive features folder. And if you are deleting a sub site, then I would recommend you to check if the site has been permanently removed from the site recycle bins. Just a hunch -> You had mentioned in your question that you removed the site and then the solution related files. If you had done in this order, probably some references were not removed. But I'm not really sure.Thanks Arut

Thats what I thought. Unfortunately its not doing it. Argh.......... M Sariman RKO Business Solutions Inc.

(a) What are the files that are not removed after solution retractions? (i.e., while your tried to search for the existing files) (b) What exactly does your solution deploy to the SharePoint Server?Thanks Arut