Hi
I created a new webpart in Visual Studio and deployed it to my sharepoint server.
It builds fine.
This new webpart is copied directly from a working webpart but when I try to add this webpart it says "The type could not be found or is not registered as safe" even though the solution builds.
Any idea how I can get more details on why it's not 'safe'?
Thanks
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
At the moment your web part DLL is in the app bin of your web application, that's why you need a SafeControl node in the web.config or modify the trust level and add a code access security to your web part deployment.
Otherwise you can deploy the DLL of your web part to the global assembly cache. The advantage is if you want your web part in different web apps you've just one source and it runs with full trust without modifying the trust level.
I did not express it very exactly in my previous post. You've two possibilities for your web part deployment:
1. app bin of your web application, then you need
- CAS (code access security)
OR (just for development)
change the trust level of you web app to full trust:
<trust level="Full" originUrl="" />
2. GAC
- SafeControl node in your web.config
e.g. something like this
<SafeControl Assembly="Microsoft.Office
+ iisreset
Hi debeho
The start of my web.config was
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<configuration>
<configSections>
<sectionGroup name="SharePoint">
<section name="SafeControls" type="Microsoft.SharePoint
I changed it to
<section name="SafeControls" type="Microsoft.SharePoint
did an iisreset and now get ...
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed.
Details: To enable the details of this specific error message to be viewable on the local server machine, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "RemoteOnly". To enable the details to be viewable on remote machines, please set "mode" to "Off".
Thanks
If you have manually deployed your customization you will have LOTS of problems. For example, it can block upgrades or updates from completing and the customization is NOT included in Sharepoint backups.
You need to get the Sharepoint SDK and read about preparing 'Sharepoint Deployment Solutions'. They are special packages built to automatically deploy and install the web part in Sharepoint web applications.
Hi hmcgeehan,
for learning it's a good test to deploy it manually. In real scenarios you'd probably deploy your webparts with a wsp-file. It depends on your backup mechanism if it's included.
adding "TypeName="*" Safe="True" " to a section name does not change the sections' nodes behaviour.
You've to add a new SafeControl node to your web.config file at the right position and don't change anything of the section names. E.g.
...
<WebPartControls DatasheetControlGuid="65BC
<SafeControls>
<SafeControl Assembly="YourNamespace.Yo
<SafeControl Assembly="System.Web, Version=1.0.5000.0, Culture=neutral, PublicKeyToken=b03f5f7f11d
</SafeControls>
<PeoplePickerWildcards>
<clear />
...
debeho: I disagree. Why spend time learning something you don't need day to day? Many Software Development books talk about improving quality by always simulating real-world conditions during design and development.
Unless every single change is rolled back when you actually try to do it the right way using WSP files it might not work properly.
Business Accounts
Answer for Membership
by: trax75Posted on 2009-10-29 at 04:22:53ID: 25692404
Hi,
you need a Safe-Control entry in yopur web.config file. Just take a look at the web.config of your websites, you will find some entries for safe controls already, copy one and chnage the name to your webpart.
cu
Torsten