IDC资讯中心
my experiences with asp+ pdc bits
now that the asp+ sdk "pre-beta" has been released to the masses. many people are scrambling to get it
installed and start to play with c#, asp+ and many other toys that come with the sdk. being the
webmaster of aspfree, ive had the privilege to work with two versions of asp+ builds. and i may add, how
stable both versions have been! its definitely been an experience, this article i hope to express some of
the things to help guide individuals who have to install and support this in their environment.
first of all, "dont install on your production servers!!", i cant stress this enough, this is "pre-beta"
software. microsoft will not support pre-beta software. aspfree is "production" i guess, but it doesnt
hurt anything if the site crashes or some pages dont display. the world wont come to an end, i use this
environment to learn new technology and share with others. i do have a development machine that i test
things before installing on the server that runs aspfree. some of the tricks i share in this article
are just my own experiences. these are the things i found helpful in keeping the samples up and working
for my visitors on aspfree.com.
how do i get asp+ installed then?
before id do anything, do a complete backup…even on your development machine. id recommend a fresh
built machine with windows 2000 and iis 5.0, then install ie 5.5 and lastly the pdc asp+ bits. many of
the newsgroups i monitor, some people are having issues if they installed the pdc visual studio 7 beta
then trying to put on the asp+ sdk. i cant comment to this because i havent installed vs 7 beta. all i
can say install in this order, a fresh install of windows 2000 w/iis 5.0, ie 5.5 and pdc build of asp+ .
things should work fine!.
what if i have classic asp applications on my server?
if your installing asp+ on a development machine with existing traditional asp applications, things will
work just fine. ive installed the asp+ bits many times and have yet to blow up any of my asp pages.
asp+ is designed to run side-by-side with existing asp pages. if you doubt this claim, view aspfree.com.
since day one, ive mixed .asp and .aspx pages together with no problems at all!
the first build story
we had a couple of small issues with the first build that was installed on aspfree. it ran pretty good
for about a week or so then we had a few odd things happen. being "pre-beta", id expected this to happen
sooner. i was very happy how stable the betas were and the small amount of issues i really had! when
the samples would die or some other error popped-up, id re-compile the samples and that would take care
of them. considering the traffic load aspfree.com visitors put on them, they held up very well.
you ask how did i re-compile the samples?
1. open a command prompt.
2 map to the ngwssdk\samples directory. if you took the default install, its c:\program
files\ngwssdk\samples directory.
3. run nmake /all this will compile all of the samples again.
another trick i found helpful when weird errors would come up, id use the "kill.exe" command that comes
with the nt/2000 resource kit. this allows you to terminate processes without restarting the server.
to "kill the asp+" process,
open the task manager (right click on the start-bar)
find the process xspwp.exe and/or the pid(process identifer)
open a command window (start, run, cmd)
type in "kill xspwp.exe" or "kill xxxx(4-digit id number)
here is a picture of what im referring too.
using the kill command has proved useful in both builds of the sdk that has been used on aspfree. the
1st build was somewhat buggy and once in awhile things basically stopped working. the pdc build, the
one microsoft just released to the world this week, is much more stable and i havent had any problems.
other strange things such as "this evil process, null string in xxx" or whatever the error. usually
killing the xspwp.exe process and letting another one start up usually fixes things. please keep in mind
this article is based on "pre-beta" software, using the kill command to fix these problems are rare now
with one exception.
what is the xspwp.exe process?
this is the worker process that handles all of the asp+ tasks.
using the kill command to help clean up virtual memory
now this part is my own twisted way i came up with to keep the virtual memory down on my server. another
thing you could do is add more memory. i however didnt have this luxury right away so i had to invent
something. because the pdc build is "pre-beta", bugs are bound to pop up. when the asp+ bits gets
installed, under the c:\winnt\complus\v2000.14.1812 is the global config.web. there is a section in the
config.web that is called iisprocessmodel. this part allows for configuring how much of the server
resources is used, how long the xspwp.exe process will live before another one is spun up etc.. now
please dont take these numbers and ones to use. these are just samples!
after consulting with microsoft, they suggested i try adjusting the timeout, requestlimit and
memorylimit.
timeout: is for how long before a new xspwp.exe will be spun up.
requestlimit: is a way to configure how many requests are handled before another process is spun up.
memorylimit: is a way to constrain so it doesnt suck all your virtual memory.
the nice thing ive seen after playing with different settings is this nice little error "evil process
didnt release lock on file! undone: rip or fix this exception". we emailed this error into microsoft and
they fixed it. the fix is probably going to be incorporated into the beta that is coming out. once i
changed the numbers back to the default, which basically are infinite numbers. things worked fine.
in the mean-time, i run a scheduled kill command to not only keep the xspwp.exe file from taking all
available virtual memory. so far, this hasnt caused any adverse side affects to the samples and things
seem to be running fine!
in conclusion
i hope these article doesnt scare you, i meant what i said. "dont install on your production
servers!!". your administrators will probably wonder why are they being called to support a beta
product. this article doesnt cover the many things that already work out of the gate, dynamically
installing dlls on the fly, caching to name a few. my opinion of this beta is such that enough of the
features work out of the box. take advantage of this period to start learning how the "next generation" of
web development will be done.
would i run a production environment on the current build? no!
is the current build very stable? yes!!
im in a unique position with having this installed on aspfree. im not only learning how to be a
developer of asp+, but also how asp+ will live on the server. im confident in the future builds,
microsoft will have the performance and resource management needs taken care of. again this is "pre-beta"
software, but this is such a revolution and so many of the features work now! this head start will help
the developer community take advantage of this awesome new technology. any questions or comments let me
know!
steve schofield
steve@aspfree.com
