Geeks With Blogs

Tangible Thoughts SharePoint, MOSS? and all the other questions

Deploying WebParts after you make a build is a bit of a hassle especially because you have to leave you IDE to do a couple of things.

The basic process is you need to

1. Compile

2. Install the assembly to the GAC

3. Copy assembly to c:\inetpub\wwwroot\bin

4. Recycle the MS SharePoint default app pool - to invoke the new instance of the assembly

-> Typically you will have to switch between VS.NET, InetMgr, and the command prompt.

So here’s what I do.

1. My WebPart projects have their default output path to c:\inetpub\wwwroot\bin

2. On the tools menu I have an external tool for Gacutil

·        Command - C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\gacutil.exe

·        Argument - /i  $(TargetPath)

·        Keyboard Accelerator - i

3. I have another external tool that would run the following JavaScript through WScript

var appPoolName = WScript.Arguments(0);
var objAppPool = GetObject("IIS://localhost/w3svc/AppPools/" + appPoolName);
WScript.Echo("Recycled " + appPoolName);

                thanks goes to David Wang for the above snippet.

·        Command - C:\WINDOWS\system32\wscript.exe

·        Argument - <PATH to JavaScript><SPACE> <APPPOOL Name>

·        Keyboard Accelerator – y


My Build process = Ctrl + Shift + B, Alt + T + I, Alt + T + Y


Posted on Thursday, January 8, 2004 6:40 AM SharePoint | Back to top

Comments on this post: A simplified WebPart build process.

# re: A simplified WebPart build process.
Requesting Gravatar...
You might be able to use my little windows service.. Then you could potentially build with "F5" :)
Left by Mads Nissen on Feb 03, 2004 10:00 AM

Your comment:
 (will show your gravatar)

Copyright © Tariq | Powered by: