asp+ my experiences with asp+ PDC bits
Now, 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, I ' ve had the privilege to work with two versions of asp+. And I may add, how
Stable both versions have been! Its definitely been a 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.
All, "DON ' t INSTALL on YOUR PRODUCTION servers!!", I can ' t stress this enough, this is ' Pre-Beta '
Software. Microsoft would not support Pre-Beta software. Aspfree is "production" I guess, but it doesn ' t
Hurt anything if the site crashes or some pages don ' t display. The world won ' t come to a end.
Environment to learn the new technology and share with others. I do have a development machine 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 I visitors on aspfree.com.
How does I get asp+ installed then?
Before I ' d do anything, do a complete backup...even on your development. I ' d recommend a fresh
Built machine with Windows 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 can ' t comment to this because I haven ' t installed VS 7 Beta. All I
Can say install in the order, a fresh install of Windows? 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 ASP traditional, applications
Work just fine. I ' ve installed the asp+ bits many times and have yet to blow all of my ASP pages.
Asp+ is designed to run side-by-side with existing ASP pages. If You are doubt this claim, view aspfree.com.
Since day One, I ' ve mixed. asp and. aspx pages together with NO problems at all!
The story
We had a couple of small issues with the ' the ' is installed on Aspfree. It ran pretty good
For about a week or so then we had a few odd things. Being "Pre-Beta", I ' d expected this to happen
Sooner. I was very happy how stable the beta ' were and the small amount of issues I really had! When
The samples would die or some other error popped-up, I D re-compile the "samples" and that would take
of them. Considering the traffic load aspfree.com visitors put on them, they held up very.
How do I did I re-compile the samples?
1. Open a command prompt.
2 Map to the Ngwssdk\samples directory. If you are took the default install, its c:\program
Files\ngwssdk\samples directory.
3. Run Nmake/all this would compile all of the samples again.
Another trick I found helpful when weird errors would up, I ' d use the ' KILL. EXE "command that comes
With the nt/2000 Resource Kit. This is allows 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)
This is a picture of what I ' m referring too.
Using the KILL command has proved useful in both builds of the SDK this is has been used on aspfree. The
1st build is somewhat buggy and once in awhile things basically stopped. The PDC build, the
One Microsoft just released to the "World" this week, are much more stable and I haven ' t had any problems.
The 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. Please keep in mind
This article was based on "Pre-Beta" software, using the KILL command to fix these problems are rare
With one exception.
What is the XSPWP.exe process?
This is the worker process so handles all of the asp+ tasks.
Using the KILL command to help clean up virtual memory
Now here is my own twisted way I came up with to keep the Virt
