Intercept Vector's Dynamic XML Weather

I came across an ASP Table Editor utility at 2eNetWorX. I have hacked together pages to execute SQL statements numerous times, so I know that this type of utility is extremely valuable. There are many other utilities on this site.

I have a feeling that I'm going to want to read this real soon...

Don XML has identified a bug that affects me. I just got the call yesterday and found the cause today. Could be a lucky day...

I couldn't believe it! If I'm not the last one, then try d.setDate(d.getDate()+1). At least now I wrote it down so I can find it when I need it again.

I was a bit disgusted with the FrontPage server admin. But, with time always a precious resource, I kept throwing together quick pages in the program. Now, a month later, I have to admit that it is a very useful program. The Page Banner and Link Bar components are nice. The Navigation pane that drives those components is very nice. The Shared Borders are a time saver. I wish the HTML editor would color-code ASP scripts. I'm using it. Early versions did not impress me. FrontPage 2002 does impress me. I'll have to see what's new in 2003.

I went looking for a bug tracking system today. Found a good resource site at Fuzzy Software. I ended up with the basic edition of ProjectApp and KnowledgeShare from ASPapp.com.

If you haven't seen it yet, Yager's column in InfoWorld is very good.

I'm not going to be relying on FrontPage server extensions for security on a client page as I had intended. I don't know if I'm trying to use them incorrectly, or if the ISP implemented it correctly. I repeatedly tried to have a subweb with different permissions than the root web. Whenever I tried, the subweb would end up with no adminstrator. The only fix was to un-install the extensions. I going to change the pages to use a login form and cookies for the authentication. FP failed me.

If you are working in a web project in Visual Studio.Net, the Add New Item dialog does not include an ASP file type. However, VS.Net does understand the file type. Click on the File | New menu, then choose the Script category. Active Server Page is the first template listed. With help from an article by Chris Sells, I created the procedure to make the ASP template available to Blank and Empty Web Solutions. These procedures assume that you installed VS.Net to the default location of C:\Program Files\Microsoft Visual Studio .NET\. If you didn't, then adjust the paths accordingly. All of the files mentioned are plain text. Make backup copies first!

Blank Solution
1.) Copy the file asppage.asp from [InstallDir]\Common7\IDE\NewScriptItems to [InstallDir]\Common7\IDE\NewFileItems.
2.) Open [InstallDir]\Common7\IDE\NewScriptItems\NewScriptItems.vsdir.
3.) Select the line containing asppage.asp
4.) Paste the line into file [InstallDir]\Common7\IDE\NewScriptItems\NewFileItems.vsdir

Empty Web Solution
1.) Create a file name ActiveServerPage.vsz in [InstallDir]\Vb7\VBProjectItems
2.) Enter the following:
      VSWIZARD 6.0
      Wizard=VsWizard.VsWizardEngine
      Param="WIZARD_NAME = ActiveServerPage"
      Param="WIZARD_UI = FALSE"
      Param="PROJECT_TYPE = VBPROJ"
3.) Open the file [InstallDir]\Vb7\VBProjectItems\Web Project Items\WebProjectItems.vsdir
4.) Add the following line. (Refer to the VS.Net documentation about VSDir files for an explanation of the values.)
      ..\ActiveServerPage.vsz|{164B10B9-B200-11D0-8C61-00A0C91E29D5}|ASP Page|1|Active Server Page|{164B10B9-B200-11D0-8C61-00A0C91E29D5}|4520| |ASPPage.asp
5.) Open the file [InstallDir]\Vb7\VBProjectItems\Web Project Items\Web\WebWebProjectItems.vsdir
6.) Add the following line. (Refer to the VS.Net documentation about VSDir files for an explanation of the values.)
      ..\..\ActiveServerPage.vsz|{164B10B9-B200-11D0-8C61-00A0C91E29D5}|ASP Page|1|Active Server Page|{164B10B9-B200-11D0-8C61-00A0C91E29D5}|4520| |ASPPage.asp