Question

I have a WSS site on a shared third-party host.

I have a solution with some custom controls -I then use the SmartPart web part to show these controls.

Here is the problem -I update the code and publish the solution to the remote host. But then I see the results of the “old” assembly.

I tried everything and the only solution is to change the name of the controls’ classes.

I am not sure where this is being cached -and how could I clear it.

Thank you for your help.

Answer 1

Usually there is no caching anywhere when you follow a complete retract/delete/add/deploy cycle of the solution package. But first of all I would make sure that the package you are deploying actually has the proper version of the code. To do so rename the package to *.cab, extract the assembly and check the changed code in Reflector. Once you know that you have the correct assembly in the solution package make sure to retract and delete the previous wsp on the SharePoint server. For only updating an assembly a solution upgrade should be fine – but try the full retract/delete/add/deploy thing just to be on the save side.

I take it that you do not have physical access to the SharePoint server. But in case the above fails your assembly might be cached in the frameworks’ temporary ASP.NET files or not properly removed from GAC/BIN folder. To reset those you need an administrator to do an IIS reset and then delete (before the site is being used again) this folder: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files and check BIN/GAC folders for the assembly.

Let me know if this helps…