|
Home > Jeff's Blog
|
|
9/21/2007When you create or purchase a new web part you have a choice whether to install it for all web applications on the server (in the GAC) or just for specific web applications.
Installing the GAC is the simplest approach, but it's not the one generally recommended by Microsoft due to the security risk of running the assembly in full trust.
9/11/2007I started a new mini-project developing some webparts. Basically, I decided to collect some of the small pieces I've created over the years in a single assembly that targets WSS 3.0. As I go, I thought I'd post some of the experience in the hopes folks might find them useful.
First, don't do these things:
- Include Javascript procedures that use simple names like "GetItem" -- that name is used by core.js and it took me forever to figure out the client-side error. To avoid collisions, prefix your Javascript procedure with the webpart name or something, like "drp_GetItem".
- Use autoincrement (*) in the assembly version number. Changing the version each build requires you to recreate your test page after each build. Instead use a static version number and manually increment it when you release to testing and to production.
- Test only on IE. Use Firefox, IE 6 and 7 if possible. Firefox is great for figuring out client-side script issues.
More later... |
|
|
|
|
|