method one:
7. Add a CAB installation package project to the same Solution, join the "Main Output" and "Content File" of the project.
8. Generate the entire SOLUTION, confirm that both projects have successfully compiled.
Add Web Part
Use the following method to deploy and add "WPHTTPRequest.dwp" Web Part:
Stsadm.exe -o addwppack -filename path_to_httpRequestCab.cab
1. Stsadm.exe defaults in the / program files / common files / microsoft shared / web server extensions / 60 / bin folder.
2. Need to change PATH_TO_HTTPREQUESTCAB.CAB to the specific path name, such as C: / HttpRequestCab.cab
Copy the wphttprequest.dll file under C: / Inetpub / wwwroot / bin, and remove the wphonetpRequest.dll file under C: / INETPUB / WWWROOT / BIN at the same time.
After successfully adding this web part to the SPS2003 Portal page, we can edit the added Web Parts by clicking "Edit Page" -> Modify Share Page "->" Modify Shared Web Parts ". Add an address to the URL in a personalized property, such as http: //server/page.asp, then click OK.
Method 2:
Deploy Web Part to BIN directory
The so-called "WEB Part deployment in bin directory" means that the DLL file created by the WebPart project is not copied to the system's GAC, but directly in the Interpub / Woort / bin directory. This is these benefits:
1, you can debug directly
2, you can take effect directly after modification, no need to restart IIS
3, deploy it simple, do not need to install the CMD command line, you can create new WebPart from the SPS management interface.
Deployment steps:
1. Copy .dwp and .dll under InterPut / wwwroot / bin (it is best to set the output directory of the project to this directory so that you can take effect immediately, it is finished, compiled, from the IE browser Can be accessed to change?
2, modify the web.config file, join
3, modify the site trust level is Full, (this is certainly available in the test environment)
OK.
Enter the SPS Management page, create a new WebPart, then put the WebPart on the web page is OK.
