Use SharePoint for the first time. It is a portal website, but it has two concepts: all its files and configurations are in SQL, virtual files, and Microsoft calls it ghost pages. They can only be changed from FPS, However, after the changes, they seem to have directly become normal pages. .
It contains two databases: content database and configuration database, which cannot be found in sqlserver manger, because they are $ share and can only change their names in Admin consol. If you want to view, you can only export data.
Design functions and interfaces required by users and common websites Program The design is not the same. Each of his modules is a webpart, and the overall page is a functional page composed of the webpart specified by the user. That is, the aspx File Created in WSS is just a webpart container.
Use. Net to develop webpart, compile it into a DLL, and then import the DWP file. Use the tool. Net (C #) webparttemplate.
Generally, it can be developed according to the corresponding specifications. After compiling, test the DLL file to the path X: \ Inetpub \ wwwroot \ bin, and then configure the new assembly in the X: \ Inetpub \ wwwroot \ WEB. config file. <Safecontrol Assembly = "editdata" namespace = "editdata" typename = "*" Safe = "true"/>. Webparts with some special features must be used only when the security level of WSS is reduced. For example, connect to sqlserver. You can use these "insecure" webparts after registering them in the corresponding configuration file. X: \ Inetpub \ wwwroot \ bin \ Web. <trust level = "wss_minimal" originurl = ""/> (final) in config, then wss_minimal is the security configuration file currently used by WSS. The path is <trustlevel name = "wss_minimal" policyfile = "C :\ Program Files \ common files \ microsoft shared \ Web Server Extensions \ 60 \ config \ wss_minimaltrust.config "/>
Find the file to open and register the corresponding security information <securityclass name = "sqlclientpermission" Description = "system. data. sqlclient. sqlclientpermission, system. data, version = 1.0.5000.0, culture = neutral, publickeytoken = b77a5c561934e089 "/>
Add <permissionset class = "namedpermissionset" version = "1" name = "ASP. NET">
<Ipermission class = "sqlclientpermission" version = "1" unrestricted = "true"/>
If you find it troublesome to change it, you can trust them all in one breath. Change <trust level = "wss_minimal" originurl = ""/> to <trust level = "full" originurl = ""/> (case sensitive) however, the security level is meaningless.
From: http://www.cnblogs.com/Mint/archive/2005/09/13/235938.html
