The guide you are following is for deploying a solution file to a server. While you are creating the webpart in your development environment, I wouldn't bother packaging it up each time.
Your most common development path will probably be (the "manual" way):
- Write some code in your webpart
- Recompile webpart
- Install the DLL into the GAC by
- Drag and drop from your Debug directory into the GAC (Start -> Run -> assembly)
- OR opening the Visual Studio Command prompt and using
gacutil /i "path/to/mywebpart.dll"
- Run an
IISRESET
command
It is important to note that your solution already took care of registering your webpart as a safecontrol in the web.config.
When you are ready to deploy to QA or Production, you would build a release copy of your DLL and then package it up into the solution.
If you have Visual Studio 2008, I would also recommend the Visual Studio extensions for WSS 3.0. It gives you a couple templates that are very useful and allows you to write, package, and deploy a webpart in solution file all from within Visual Studio.
- Create a new Web Part project (this is a VSeWSS project template)
- Right click on your project's properties, go to the Debug tab, and set "Start Browser with URL" to your SharePoint site (your account will need all the necessary rights to deploy code)
- Write some code!
- Right click on your project and click Deploy
- Add the web part to the site's web part gallery:
/sites/SiteCollection/_catalogs/wp
.
- Add the web part to a page
- Repeat #3 and #4!