Deal easily with Safe Controls problems in SharePoint with Visual Studio 2010
You get the following error when you try to add a custom WebPart in to your site: " Type is not registered as safe " Error Message This means that you: Don't have an web.config entry for your dll have a wrong web.config entry for your dll The 2nd reason is more often, especially when you develop a WebPart in Visual Studio and change the default Class or NameSpace names. Steps to solve the problem 1. Check your web.config This step is only to check if there is a web.config entry when you deploy your solution. For this deploy your solution into the farm. Open your web.config file in (C:\inetpub\wwwroot\wss\VirtualDirectories\youwebapp\web.config). Search after "<SafeControls>" and check if your dll is listed there and if so check if all parameters like PublicKeyToken, NameSpace or DLLName are correct Safe Control Entry in Web.Config Tip : If oyu deployed your assembly into the GAC, you can check the "PublicKeyT...