You can deploy your DLLs either to GAC or IIS Home BIN directory. For those
deployed to GAC it has full trust by default but you still need to add the
SafeControl entry in web.config. For the ones in IIS BIN directory it’s using
CAS security. You can either set <trust level=”Full”… in your web.config or add
the DLL info in custom policy file. By default Sharepoint is using <trust
level=”WSS_Minimal” which then points to an actual configuration file in this
section:
<securityPolicy>
<trustLevel name="WSS_Medium" policyFile="C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\12\config\wss_mediumtrust.config"
/>
<trustLevel name="WSS_Minimal" policyFile="C:\Program Files\Common
Files\Microsoft Shared\Web Server Extensions\12\config\wss_minimaltrust.config"
/>
</securityPolicy>You can also create your own security configuration file and set the <Trust Level=”MyOwnConfigFile”. Cheers. Tommy Segoro Sharepoint Specialist Practice Lead [cid:[email protected]] L7 Solutions Pty Ltd www.L7.com.au<http://www.L7.com.au> T: +61 8 9221 7744 F: +61 8 9221 8199 M: +61 404 457 754 Ground Floor 256 Adelaide Terrace Perth WA 6000 PO Box 3044 Adelaide Terrace WA 6832 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Williamson Sent: Sunday, 23 November 2008 2:56 PM To: [email protected] Subject: Re: [OzMOSS] ASP.Net Controls in MOSS Don't they have to go in safecontrols? It sounds like you need to start backing up your web.config with your other backups. On Sun, Nov 23, 2008 at 2:13 PM, Matthew Cosier <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: If the masterpage is hosting some external/custom built ASP.NET<http://ASP.NET> controls and they are defined within a set of strongly named assemblies, you can just install them into the GAC and it should work fine. Might I suggest you try contact the developers, to get a better insight into the custom development? You might also be missing other resources or dependencies (assemblies, configuration, etc). Matthew Cosier On Sun, Nov 23, 2008 at 5:27 AM, Uzma Naz <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: I have an unusual situation. I've migrated contents from an existing SharePoint farm using content deployment job. The new farm on a new server is running well, I can see that all contents have sucessfully been transferred using SiteManager.aspx but I cannot view any pages. Looking into the site further, the master page has ASP.Net controls and I have found dll files which relate to the site. So my question is what steps do I need to take in order to view my page correctly? I've seen that I must register the assemblys, using strong names and using GAC. That is pretty much alien to me as I am not a .Net developer. Any advice will be very, very helpful. Also, you'd think with a content deployment AND a full farm backup/restore that you could replicate sites but guess it isn't that easy (darn SharePoint!) Many thanks. Uzma ________________________________ Win £1000 John Lewis shopping sprees with BigSnapSearch.com Search now<http://clk.atdmt.com/UKM/go/117442309/direct/01/> ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com<http://mailenable.com/> ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com<http://mailenable.com> ;3 I'(ڮ˛ʢm竢kaɢ۞֦z˚暲Kh˰خ˛ʢm欶Б>‑益f隮W ;3I'(��.�˛���m���ka��b�� �֦z����rKh����p��n�˛���m欶����r�����u��j)^���y�&
<<inline: image001.jpg>>
