ASP4HS Home

Asp4Hs: HomeSite Tips and FAQs

[ Asp4Hs | Add-On's List | Articles | WishList | Links | Tips/FAQs | Submissions ]
  1. Critical and Most Common FAQs
    1. FAQ: What do I need to view ASP in HomeSite?
    2. FAQ: What do I need to view PHP in HomeSite?

    3. FAQ: Does Homesite 5.x only work under an Administrator account?
      FAQ: What user permissions do I need for HomeSite under WinNT/2k/XP?
       Updated!

    4. FAQ: Does Homesite work in Windows Vista?  Updated!

    5. FAQ: Does Homesite work in Windows 7?  New!

    6. FAQ: Resources for those having trouble with HomeSite and WinXP SP2

    7. FAQ: Is Adobe/Macromedia still actively developing HomeSite? Will they ever?  Updated!
    8. FAQ: What is HomeSite+? How is it different from HomeSite?
    9. FAQ: Can/Will Macromedia make a version of HomeSite for the Mac? or Linux?
  2. HomeSite Feature Extension FAQs
    1. FAQ: Writing your own Syntax Coloring Parser Scripts
    2. FAQ: Writing or Converting Help Sets for HomeSite Use
    3. FAQ: Making Added Help Sets Searchable
    4. Tip: Adding Help Docs to HomeSite
    5. Tip: Decompiling Compiled HTML Help Document Sets
    6. Tip: Linking PWS/IIS Docs into the HomeSite Help System
    7. FAQ: How do I find additional Spell-Checker Dictionaries for HomeSite/CFS/JRS
    8. Tip: Quick Scripts for HS functions
    9. Tip: Clearing VTML Cache
    10. See also the faqs on Scripting HomeSite
    11. See also the many articles by others on HomeSite topics and features.
  3. HomeSite User Interface FAQs
    1. Tip: Learn to use HomeSite Projects
    2. Tip: Learn to use HomeSite's Built-in FTP
    3. FAQ: Backing Up Color Coding Schemes
    4. FAQ: Adding Edit with HomeSite as an Explorer Right-Click Option
    5. FAQ: Adding HomeSite/Studio as an HTML editor in MSIE.
    6. Tip: Using Netscape or Mozilla or Firefox as the internal browser
    7. Tip: Speed Editing by using Keyboard Shortcuts to Snippets, Scripts and Toolbar buttons.
    8. Tip: Speed Editing by using the Code Template feature.
    9. Tip: Sharing components, snippets, templates in Homesite/Studio
    10. Tip: Change the date format on the RMB menu | Insert Date/Time
    11. Tip: Modifying default image extension for opening files
    12. Tip: Re-Docking Resource Windows
  4. HomeSite Feature Use FAQs
    1. For a better understanding of HomeSite features, see the Macromedia HomeSite 5 Feature Tour.
    2. Tip: HomeSite Server Mappings
    3. FAQ: How do I get HomeSite working with my Source and Version Control software? (CVS/RCS/ClearCase/etc)

    4. Warning: Do Not use HomeSite's Design View with ASP or PHP pages.
    5. Warning: Be very careful using CodeSweeper with ASP or PHP pages
    6. Warning: Be very careful using HTML Tidy with ASP or PHP pages
    7. Warning: Common ASP Security Issues
    8. See also the many articles by others on HomeSite topics and features.
  5. Scripting HomeSite
    1. Tip: HomeSite scripting references and examples (WSH Scripts / ActiveScript)  Updated!
    2. Tip: Script for custom toolbar button that passes folder path of active doc  New!
    3. Tip: Quick Scripts for HS functions
  6. Odds and Ends
    1. Tip: Getting CF / CFMX Updates for Studio/HomeSite
    2. FAQ: How can I run more than one instance of HomeSite at the same time?
    3. Tip: Learn to Check and Read the References
    4. FAQ: Are there any "Built with HomeSite" button images?
  7. HomeSite Tips Elsewhere
    1. Ben Forta's Blog: Tips (CF Studio)  New!
    2. Charlie Arehart  New!


FAQ: What do I need to view ASP in HomeSite?
I'm pretty new to ASP and I'm having trouble with being able to view ASP in Homesite. Is there something I need to download either from Microsoft or Macromedia that will allow me to view the ASP locally? I can't learn ASP/VBScript very well if I can't see if I'm doing it right.

Answer: There are two things you need; a local webserver that can execute ASP and HomeSite's server mapping feature.

Most people who need ASP run PWS (personal web server) on Windows 98/95/me or IIS on Windows NT/2k/XP. Here is a link to download PWS though it may already be on your Windows install disk. It's free.

Setting up PWS is fairly easy, but there are good directions in these articles to help you get going.

The second part, HomeSite's server mapping feature, lets you tell homesite to use the path through the local webserver when viewing files, instead of just the local file path. For directions on setting it up, see the Macromedia article; Setting up Server Mappings in HomeSite or Technote: How to setup a server mapping in HomeSite.

Once you get going, you might check out some of the other links here on Asp4Hs. There are a lot of useful things to help you get going.

Note that "local webserver" can be a fairly broad term. For instance, if you have a drive mapped to an file server where the files in the directory are also viewable via webserver software on that machine, you can use server-mappings. They don't have to be strictly local, as "on your machine."
(Example: my N: drive maps to \\myserver\mysite\. The webserver software on myserver provides http://myserver.mydomain/mysite/)

FAQ: What do I need to view PHP in HomeSite?
Setting up PHP to work well with HomeSite editing is very similar to the ASP setup. There are two things you need; a local webserver that can execute PHP and HomeSite's server mapping feature.

So, see the FAQ: What do I need to view ASP in HomeSite? Then check out the tutorial links at the bottom of php4hs. There are several excellent write-ups teaching how to set up PHP with HomeSite and various local webservers.

FAQ: Does Homesite 5.x only work under an Administrator account?
FAQ: What user permissions do I need for HomeSite under WinNT/2k/XP?
Question: what permissions are needed for users to run HomeSite on machines running WinNT, Win2k or WinXP? Install HomeSite when logged in as an Administrator user. You'll have to also grant access to some registry keys or when a normal user wants to start the app, they may only get the migration wizard and that's it.

Install HomeSite as Admin user.
Then, you should grant full access to the following keys:

This applies to WinNT, Win2k and WinXP.
See also TechNote 17365: "Win2000/NT Users get an Error when trying to Launch HomeSite or Studio 4.5.1"

10/2010 Update: Note that in MS Vista, users have had a variety of permissions and installation rights issues. There is a lot of useful information on how they have solved those issues in this thread: Adobe Forums - Thread 185500: HomeSite and Vista.

From these threads (thread, thread)

FAQ: Does Homesite work in Windows Vista?

Yes, HomeSite 5.x will work under Windows Vista, but you need to take some extra steps during install to get it set up correctly and to give it the right permissions. Earlier 4.x versions of HomeSite may or may not work well in Vista, but the setup details should be similar.

See this KB Technote: HomeSite compatibility on Windows Vista.

The HomeSite support forums also have some threads where users have provided excellent info on getting this working. In fact the technote was written based on their findings.

10/2010 Update: Note that in MS Vista, users have had a variety of permissions and installation rights issues. There is a lot of useful information on how they have solved those issues in this thread: Adobe Forums - Thread 185500: HomeSite and Vista.

If you have additional information on this, please email me and/or post it in the forum. Thanks!

FAQ: Does Homesite work in Windows 7?

HomeSite 5.x will *probably* work under Windows 7, but you may need to take some extra steps during install to get it set up correctly and to give it the right permissions. Earlier 4.x versions of HomeSite may or may not work well in win7, but the setup details should be similar.

See this KB Technote: HomeSite compatibility on Windows Vista.

The HomeSite support forums also have some threads where users have provided excellent info on getting this working. In fact the technote was written based on their findings.

10/2010 Update: Note that in MS Vista, users have had a variety of permissions and installation rights issues. There is a lot of useful information on how they have solved those issues in this thread: Adobe Forums - Thread 185500: HomeSite and Vista.

10/2010 Update: A thread has been started on the topic of HomeSite and win7. It would be a good place to check for what other users are seeing, and what solutions they have found. See Adobe Forums - Thread 504297: Homesite and Windows 7, anyone?.

One HS user reported "I had to go to Microsofts site and download the two files for XP Virtual machine mode. Then run that and Homesite works in the Virtual machine mode."

If you have additional information on this, please email me and/or post it in the forum. Thanks!

FAQ: Resources for those having trouble with HomeSite and WinXP SP2
While the great majority of HomeSite users are having no problems with the WinXP SP2 update, a few are, so here are some resources for those having trouble.
FAQ: Is Adobe/Macromedia still actively developing HomeSite? Will they ever?

12/2007: I don't know.

The most 'Recent' updates was the version 5.5 update release in 9/2003. Since then, and since Adobe bought Macromedia there haven't been any releases (yet). That said, they are still selling it.

My personal advice is: If you really want to see HomeSite actively developed and upgraded, tell Adobe. I believe the only way they will decide to devote resources to it is if they hear from enough HomeSite users who are willing to pay for HomeSite upgrades.

Either way, HomeSite was designed originally to be so incredibly extensible and customizable that users have tweaked it and have written add-on's like those on this site to keep it reasonably up-to-date. Even if it isn't upgraded beyond version 5.5, it is *still* a very good tool for website developers. If it doesn't do something you need, check the add-on's here and see if you could use one, modify one or write your own to meet your needs.

FWIW, we have an interesting forum thread discussing what we might want to improve or add if HomeSite is upgraded beyond v5.5.
Thread: HS General Discussion: Homesite Future - What would you want changed?

(date written?) There has been a lot of confusion and discussion about the future of HomeSite as a separate product or whether it might be merged completely into Dreamweaver MX by Macromedia. FWIW, the 'official' word on it is at HomeSite - Dreamweaver MX FAQ and the CF Studio FAQ. If this is not satisfying or understandable to you, come join the discussions on the HS forum. Hopefully we won't have to migrate to DWMX.

FAQ: What is HomeSite+? How is it different from HomeSite?
You can read Macromedia's answer to this question here.
What exactly is Macromedia HomeSite+?
"Macromedia HomeSite+ is a separate product included with Dreamweaver MX that combines the functionality of Macromedia HomeSite 5 and ColdFusion Studio 5, while adding support for the newest ColdFusion MX tags through new tag editors and tag insight menus. Macromedia HomeSite+ is not sold as a separate product and is only available with Dreamweaver MX."

Basically it is HomeSite with the additional ColdFusion stuff. In other words, it is CF Studio, but sold now only as a part of DW/MX (PC-version only). I am trying to get MM to write up a technote on exact differences between regular HS and HS+.

FAQ: Can/Will Macromedia make a version of HomeSite for the Mac? or Linux?
Short answer: No. You can read Macromedia's answer to this frequent question in this thread. It's a good discussion of why the answer is 'no.' Basically it would be very difficult and expensive to port HS to other operating systems.

As Matt Brown of Macromedia says: "Applications are written in different languages like C or Java or whatever. In this case HomeSite is written in Delphi and there is no cross platform compiler that the engineers have come across that will allow them to port the product. It would require a full rewrite from the ground up and there are simply not resources to do that unfortunately. HS is excellent, but it is Windows only. If you want an excellent Mac text editor and Dreamweaver is not your thing then please take a look at BBEdit which is a world class product."

FWIW, the answer has always been about the same to the request for HomeSite for Linux.

And, to answer one other common suggestion, it's very unlikely that Macromedia would make HomeSite open source.

FAQ: Writing your own Syntax Coloring Parser Scripts

HomeSite uses the TSyntaxMemo editor component. It provides a way to customize or add syntax coloring for all sorts of languages. You write up a parser in a text editor, then HomeSite compiles it when you install it. HomeSite provides a number of parsers but there are times when a user needs something else, often a language or variant that isn't supported yet. This is when you might consider writing your own.

  1. When you've decided you have to write your own, the first information gathering stop is the TSyntaxMemo Docs and sample scripts. You'll find documentation there for the scripting language used to write the parsers and a number of examples that may be useful either as starting points or for learning.

    With permission of the author and owner, I have posted copies of the Dbrock software TSyntaxMenu docs and sample scripts. They are no longer available on dbrocksoftware.com and anyone wanting to write syntax coloring parser scripts will need the documents.

  2. Second is the tutorial written by B. Collier Jones; Creating Syntax Highlighting Parsers for HomeSite. This is a basic tutorial that provides a introduction to the process of creating and installing syntax parsers for HomeSite 4.5 and later. Runs you through a simple example parser development. Essential reading for parser work. Since Collier is an acknowledged user expert on the topic and the creator of the current ASP, PHP (and other?) parsers in HomeSite, this clearly-written lesson should be quite valuable to you.

  3. Third is to download the source script files available at Macromedia for all the existing parsers in HomeSite. These will give you a huge head start.

  4. Lastly before you dive into coding, check out the existing parsers that other users have written to see if any give you a head start or teach you things you'll need to know.

  5. Finally, once you're written a parser, please consider sharing it with others by either posting it on your own site and letting me know to link to it, or by posting to the Macromedia Developers Exchange. (under HomeSite: Color Coding Schemes)

One warning: this is generally not a trivial process, though a number of people have picked it up. If you want a particularly complex parser, you might approach B. Collier Jones or someone else who has mastered the process. You might be able to hire them to write custom parsers for your needs.

To install an existing parser, see these installation instructions Script technique to Install or Swap Syntax Coloring Parsers and FAQ: Backing Up Color Coding Schemes.

FAQ: Writing or Converting Help Sets for HomeSite Use
This FAQ provides some help and suggestions for those wishing to write html help doc sets or to convert existing docs for use in HomeSite's integrated help.

If you do a help set, please let me know or post the news on the HomeSite/Studio forums. I'd be glad to host or list it from Asp4Hs or Php4Hs. Email me if you need more help.

FAQ: Making Added Help Sets Searchable
Jon Burrows posted this this answer for how to get the HomeSite help search to look into help docs that you've added to the HomeSite/Help directory yourself. This also addresses getting HomeSite to look in your custom help sets for the help for functions when you hit the F1 key.

Note: I haven't tested this yet myself, though I think it is the correct procedure. We've requested a better (less manual) way to do this to be added to the next rev of HomeSite. ~jw

The thread custom context help also has information about adding your own custom functions to the help using 2 different methods.

Look also at the installed help docs for information on the booktree.xml file. This file seems to be used by HomeSite now to organize help docs, so modifying it may be all you need... (I haven't played with it yet and am not sure what versions use this)

Tip: Adding Help Docs to HomeSite
You can add ASP support docs that contain tags and scripts or even links to Microsoft's ASP and VB libraries to the HomeSite Help Window. You do this by adding the desired files to HomeSite's Help folder. When you want to add a tag or piece of script, click on the help tag and choose the help file that contains the code you want, then copy and paste it into your document. This works really well as you can have libraries of code right at hand. I find this faster and easier than creating new snippets. -- Brian Goldstein (Forum Thread)

See LearnAsp.Com for downloads some of the Microsoft ASP docs that we don't have in the Add-On's List yet.

Tip: Decompiling Compiled HTML Help Document Sets
According to Andy Buchanan, in this thread, you can decompile the compiled HTML (.chm) files into their original files "from the FILE menu using MS HTML Help Workshop (Download). See Decompiling a help file for details. This also explains how to decompile from the command line using Hh.exe, i.e. no extra downloads."

This would let you make sets of help docs for VBScript, JScript, ADO, etc for installing directly into the HomeSite Help directory, rather than having to use a toolbar button to launch the compiled versions.

Tip: Linking PWS/IIS Docs into the HomeSite Help System
As one user pointed out, if you have PWS or IIS on your machine, it comes with help documents. Instead of making a separate set of help docs under HomeSite/Help, you can put a single file there with links or even a META refresh jump page pointing to the installed location of the help docs. There are several advantages and disadvantages to this over copying the pages under the Help directory.

Advantages:

Disadvantages:

FAQ: How do I find additional Spell-Checker Dictionaries for HomeSite/CFS/JRS
The spell-checker options changed somewhat over major versions of HomeSite (and CFS/JRS). I'll attempt to explain the situation as it exists so far and point you to a few resources.

HomeSite /CFS/JRS v3.0x:
Uses only it's own, internal spell-checker engine. Additional spell-checker dictionaries (lexicons) are available for download from the DevEx: HomeSite: Language Dictionaries.


HomeSite /CFS/JRS v4.0x and v4.5.x:
Can use either it's own, internal spell-checker engine or the spell-checker installed with MS Office97 if it is available on that machine.

Additional spell-checker dictionaries are available for download from the DevEx: HomeSite: Language Dictionaries. These will work for HS/CFS/JRS 3.0x, 4.0.x and 4.5.x??? versions.

Note: MS Office versions after MSO97 changed the licensing or mechanism so that now other software cannot use the Office spell-checkers. HS/CFS/JRS v4.0.x and 4.5.x can use it if Office97 is present. See TechNote 17728.



HomeSite /CFS/JRS v5.x:
Uses a new spell-checker engine by Wintertree Software. Additional dictionaries licensed from Wintertree are available for download at Macromedia Dictionaries.

Note: because of the change if MS Office mentioned below, HS v5.0 no longer has the feature to use MS Office spell-checkers.

Tip: Clearing VTML Cache
HomeSite caches the info used in Tag Inspector, Tag Tips, Tag Insight, and Tag Editor so debugging a vtm can be frustrating when you make changes but the results don't seem to change. Hit Ctrl-Shift-Alt-C to clear that cache. Rerunning your vtml afterwards should use the new file. See TechNote 20621: ColdFusion Studio and Homesite: VTM Changes Are Not Immediately Applied.
Tip: Learn to use HomeSite Projects
Learn about setting up and using projects in HomeSite from this set of excellent articles.
Most articles on version 4.5.x also apply to version 5.x.
Tip: Learn to use HomeSite's Built-in FTP
Learn to set up and use the FTP (file transfer) features built into HomeSite with these articles.
Note: Most articles on version 4.5.x also apply to version 5.x.
FAQ: Backing Up Color Coding Schemes
You can back up your color coding schemes or save them to transfer the settings to another computer. All color coding customizations are stored in the registry. Found here: HKEY_CURRENT_USER\Software\Allaire\HomeSite45\CustomParserSettings or HKEY_CURRENT_USER\Software\Macromedia\HomeSite5\CustomParserSettings
... or in similar keys for other versions of the software...

Just export this key.
Here is how you do that:

  1. Start | Run | type in "regedit"
  2. Browse to HKEY_CURRENT_USER\Software\Macromedia\HomeSite5\CustomParserSettings
  3. Select the CustomParserSettings folder
  4. Then select from the top menu bar Registry | Export Registry Key
  5. Name it and save it to a place you will remember (DeskTop) as a .reg file.
  6. If you are copying these settings to a different computer, then copy that file over to that computer.
  7. Install HomeSite if it was not already installed.
  8. After installation, double click on the reg file, it will automatically update your registry and restore your color coloring customizations.

Note: this is not saving custom parsers you might have added, just the color selections that you might have chosen to use for particular coloring schemes.

(These instructions were written by Dan Zarella, Allaire Customer Support)

FAQ: Adding Edit with HomeSite as an Explorer Right-Click Option
MS Windows Explorer (the file manager, not the browser) allows you to associate multiple applications with a particular file type. In Explorer, you can select a file, then Right-Mouse-Click to pop up the context menu. You then select which application you wish or what action to perform. This procedure tells you how to add an "Edit with HomeSite" action/option for .ASP files. Obviously, this procedure can be applied to other file types.

  1. Open Windows Explorer and navigate to a subdirectory that contains files of the type you wish to add an action to.
  2. Note the name of that file type used in the Type column.
  3. Select one of the files and Right-Mouse-Click to see if there is already a default action associated with it. The action will generally be bolded and near the top of the pop-up menu. If the bolded one is "Open With" then there is no default application.
  4. If there are no actions assocated with the file type or if you want to replace the existing open action, you can add one the short way. If you want to add HomeSite in addition to other actions, then you need the longer method. (just like taxes, the short form or the long form... ;-)

The short method

  1. Select one .asp file (or whatever type you're working on)
  2. Hold in the Shift key and right-click.
  3. The pop-up menu should have "Open With" as an option. Click it.
  4. Choose the program you want to use (HomeSite) and check the box saying "Always use this program to open this type of file."
  5. Click OK.
  6. HomeSite should now be used as the default when you double-click on files of this type.

The longer method

  1. On the Explorer menu, select View | Options.
  2. Next, select the File Types tab.
  3. Find the file type name you noted in step 2 and click "Edit." (If it's not there, then click "New Type")
  4. Under actions, there will be a list of any actions that are set up. The default action will be bolded. To add a new one for HomeSite click "New" under the actions box.
  5. In the "Action" box, add a new name, like "Edit with HomeSite"
  6. For the "Application used to perform action" box, click on the browse button and go to your HomeSite install directory. Select the Homesite exe file and click ok. This should enter something like:
       "C:\Program Files\homesite 4.5\homesite45.exe"
    depending upon your install path.
  7. Add "%1" after the path for something like this:
      "C:\Program Files\homesite 4.5\homesite45.exe" "%1"
    Note that all the quotes should be there. This lets it work for paths that contain spaces.
  8. Click Ok.
  9. Select the action and click "Set Default" if you wish.
  10. Click OK several times to finish.

Explorer's ability to associate multiple apps with a file type can be very handy. For instance, you can have the default set to your main editor, but also have options for other editors you use, file checkers, compilers, etc as long as you have the correct command line parameters set up.

FAQ: Adding HomeSite/Studio as an HTML editor in MSIE.
A simple registry entry addition will allow IE5 to use HomeSite to edit html. Now you can check your ASP or Database generated HTML code using HomeSite's syntax highlighting and validation features. To enable it follow the directions in the KB article below and the next IE5 window you open up will have "Edit With HomeSite" as an option on your Edit button. See this technote for full directions and a registry change file for your installation.

See also the MS KB article: Changing Source Code Editor in Internet Explorer.

To change it for MSIE v6 and HomeSite v5 use Regedit to change the following key:

HKEY_CLASSES_ROOT\htmlfile\shell\edit\command

and the value for that key should be:

C:\Program Files\Macromedia\Homesite\HomeSite5.Exe "%1"

This assumes that HomeSite v5 is installed in the default location. Change the argument as necessary for other locations. If your install path has a space in the name, you may need to surround the path/filename with double quotes ("c:\some path\homesite.exe" "%1")

Note the quotes around the %1 parameter that makes it work for paths and filenames that might have spaces. Without the quotes, the editor thinks paths with spaces are 2 arguments instead of one and it fails.)

You can add different editors to the click-down "Edit" button list on MSIE by adding the following key:

HKEY_Current_User\Software\Microsoft\Internet Explorer\Default HTML Editor\shell\edit\command

and the value for that key should be the path to the desired editor. For HomeSite v5 with a default install path, you can use:

C:\Program Files\Macromedia\Homesite\HomeSite5.Exe "%1"
Tip: Using Netscape or Mozilla or Firefox as the internal browser
To set up Netscape (NS v6+ or mozilla, firefox, etc) as the internal browser in Homesite/Studio, follow the directions in KB article 9927.

12/2003: I'll be writing this up more when I get time to test it, but for now, see Nick Bradbury's discussion of the new installer for the Mozilla 1.5 ActiveX Control, the bit that lets you use Mozilla as internal browser for TopStyle or HomeSite. See also his informative earlier discussion on this topic.

4/2005: Some users in this thread mention that they get an error saying, "c is not a registered protocol" when they use Firefox as HomeSite's internal browser for locally-stored files.
The fix seems to be to make sure that "Use DDE" is un-checked.
Find it under Options | Configure External Browsers | Highlight Browser | Edit.
For Internet Explorer, it should remain checked.

Tip: Speed Editing by using Keyboard Shortcuts to Snippets, Scripts and Toolbar buttons.
You can speed your editing if you assign keyboard shortcuts to your most frequently used snippets, scripts, or toolbar buttons. For example, make a snippet for <% %> and assign it to Alt-A or a snippet for response.write assigned to Alt-R. It saves heaps of time once you get used to using them. -- Damian Maclennan
Tip: Speed Editing by using the Code Template feature.
You can speed your ASP editing using the code templates feature of homesite. This lets you assign small bits of code for expansion.

Jens Nilsson writes: ... a useful tool i recently discovered in Homesite when coding ASP is the "Code template" tool. I use it for a lot for the most common asp commands and it works pretty nice because you can choose where the cursor will appear after running the function. I haven't really looked in to it yet but I don't believe that feature is available for snippets is it? (yes, it is ~jw) Anyway I have assigned Shift + Ctrl + Enter to run the code template to speed things up even more which makes it very smooth to use.

As a result of all this it means that you have a very customizable tool that certainly increases your coding speed, lets you choose where the cursor will land, gives you control of what you will call the abbreviation, when to run it and what shortcut to run it with.

You can for instance call the code template when you type resp and it will give you the Response.Write "" with the cursor already inside the quote marks. Or give you an if/else/end statement. You also don't have the bother with suggestions of commands appearing when you don't want to which can be a bit annoying sometimes.

I think the Code template been underestimated and I just wanted you to be aware of it if you weren't already. Regards, Jens Nilsson

Tip: Sharing components, snippets, templates in Homesite/Studio
If you want to share snippets, wizards, templates, etc between a team, you can point Homesite to common directories. To set it up, follow the directions in the HomeSite Technote: Sharing components in HomeSite/Studio.

That technote shows the Allaire registry keys used in older versions of HomeSite. HomeSite v5+ will use
  HKEY_CURRENT_USER\Software\Macromedia\HomeSite5\FileLocations

Note that HomeSite v5 lets you set some of these via the Options | Settings | Locations dialog.

In HomeSite v5, custom templates share locations are set by this dialog, using the "New Files Repository" field. Files at the location specified there will show up in the "Shared Repository" tab when you click File | New.

Tip: Change the date format on the RMB menu | Insert Date/Time
The formats offered on the Insert Date/Time feature, found on the right-mouse button popup menu can be changed easily by changing the default format used by Windows. For example, if you prefer "September 4, 2001" to "Tuesday, September 4, 2001", go to Control Panel | Regional Settings | Date and change long date to MMMM d, yyyy. (MMMM dd, yyyy will give you a leading 0 on single-digit days).
Tip: Modifying default image extension for opening files
Question: When I open the tag editor to add an img-tag and hit the browse button to select the picture, it always defaults to gif images. I only use jpg images and have to manually select the jpg file types setting. Is there a way to make jpg default?

Edit the definition file:
   C:\Program Files\Macromedia\HomeSite 5\Extensions\TagDefs\HTML\Img.vtm

Find this line:
<CONTROL TYPE="FileBrowser" NAME="urlSrc" WIDTH="MAXIMUM" MAXWIDTHPADDING=10 ANCHOR="lblSource" CORNER="NE" FILTER="*.jpg;*.gif;*.jpeg;*.png" RELATIVE/>

This is the version I modified. I switched the positions of the *.jpg and the *.gif and now the default I get the jpg files.

As written in this thread

Tip: Re-Docking Resource Windows
In HomeSite you can un-dock or float one or more of the resource windows easily by double-clicking on the top title area of the resource window.

However, it's not clear how to re-dock them, and the HS help doesn't really tell you how either.

To dock them, you'll have to repeat this action for each resource tab.
Right-mouse-click over the area within each tab and select Move (tab-name) to Left.

Here are some screen shots illustrating this:

  1. Undocking
  2. Undocked
  3. Redocking

Note that the local file tabs may be floating with just the folders list showing. You can't get that "Move to Left" menu option if you click over the folders list, but must drag the bottom down or the folders/files list separator bar up so you can see the files list. Then Right click over the files list and select Move Files 1 (or 2) to Left..

For some reason, you may need to re-dock some of the other tabs like help or snippets before re-docking the Local Files tabs.

See also Ben Forta's tip: Prevent Accidental Resource Tab Moves.

Tip: HomeSite Server Mappings
Setup and use of server mappings in HomeSite will let you execute ASP scripts through Personal Web Server (PWS/ASP) when using HomeSite's internal viewer. See the following for more info. Server mappings can be used with any locally-run server software, whether it be PWS, IIS, apache, CFexpress, etc.

If you are using Apache and PHP, you should read Dave Alders' write-up, Setting up server mappings with HomeSite/Apache/PHP.

FAQ: How do I get HomeSite working with my Source and Version Control software? (CVS/RCS/ClearCase/etc)
There is more information at Asp4Hs: Source and Version Control about using various types of version or source control software with HomeSite. Feel free to send me info if you have more on something I have listed or something I'm missing.
Warning: Do Not use HomeSite's Design View with ASP or PHP pages.
It is a MS component and will often screw up ASP or PHP code enough to kill a page. Yes, this is ironic as both ASP and the component are MS products... talk to bill about it... In HomeSite's options, you can disable/hide the Design View tab to prevent accidentally hitting it.
Warning: Be very careful using CodeSweeper with ASP or PHP pages
Since ASP and PHP are not really tag-based, they can be really screwed up. Wil Genovese has attempted to make a CodeSweeper profile for HTML and ASP and recommends:
The CodeSweeper for ASP is limited again because CodeSweeper relies on valid tags and valid HTML. ASP tags are not valid tags or valid HTML, this tends to confuse the CodeSweeper to no end... I think the CodeSweeper for ASP is very unsafe for beginners. I did have an ASP page someone gave me and I was able to get CodeSweeper to work on it without changing the code. I would NOT list it for amateurs. Only those that know how to config CodeSweeper very well and only on a extra backup copy of code."
Warning: Be very careful using HTML Tidy with ASP or PHP pages
HTML Tidy, the additional code checker/cleaner by Dave Ragget that comes with HomeSite v4.5+ has issues similar to CodeSweeper. See the section "Limited support for ASP, JSTE and PHP" for more details.
Warning: Common ASP Security Issues
For a few of the common security issues, check out ASP Security Notes and Links: Security Information.
Tip: HomeSite scripting references and examples (WSH Scripts / ActiveScript)
HomeSite 4 and later provides an interface (VTOM) to let you write WSH (Windows Scripting Host) scripts using JavaScript (JScript) or VBScript that can automate all sorts of actions. Power users can write scripts to control HomeSite and ColdFusion Studio functions and developers can call functionality from their applications using the Visual Tools Object Model (VTOM). The VTOM is mature and well documented in the help.

To get started scripting HomeSite, see some of these:

Tip: Quick Scripts for HS functions
You can write quick scripts to get to HomeSite functions that might normally be buried down on menus... then call the script from a toolbar button for quicker use. For example, if you want a toolbar button to bring up the "Recent Files" dialog, you can use the following script. Other functions can be called easily by simply changing the keystrokes fed by the script.
Sub Main
'
' Recent Files on the Toolbar
' Author: Christian Swoboda
' Date:  2001-08-23
' 
' This tiny little routine uses the SendKeys call, 
' to reach the "Recent Files" pulldown with one click.
' Just put a custom button on your toolbar and enjoy
' (You need WSH 2.0 for this to work!)

  set WSHShell = CreateObject("WScript.Shell")

  WSHSHell.SendKeys "%F"  ' % for the Alt-Key
  WSHSHell.SendKeys "R"
 
End Sub

Thanks to Christian Swoboda for this solution, posted to the forum.

Tip: Script for custom toolbar button that passes folder path of active doc
From the thread: customizing toolbars / custom buttons

Question: Can you suggest me what is the command line parameter to pass to an external application (i.e.: windows explorer or a rename utility), so that it opens in the folder containing the file currently opened in HS

Answered by KeithC:
Here's some code that will do just that: (dunno how this message will be formatted in the forum, but you can copy & paste it into Homesite)

var oApp = Application; // pointer to application object
var oDoc = Application.ActiveDocument; // pointer to activeDocument object

function Main() {
var folderPath; // folder path of active document
// Extract the folder path from the current document's file path
folderPath = oApp.ExtractFilePath(oDoc.Filename);
// Call explorer, passing the folderpath as argument (surround in quotes)
Application.ShellToApp("explorer.exe \"" + folderPath + "\"");
}
Tip: Getting CF / CFMX Updates for Studio/HomeSite
Some people have been wanting to get various CF (ColdFusion) and CFMX reference and tag editor updates for HomeSite 4.x and 5.x. Here is some information that should help.

If you are looking for Fusedocs or Fusebox for HomeSite, see Sandra Clark's toolsets and Andy Jarrett's Fusedoc for HomeSite snippets.

FAQ: How can I run more than one instance of HomeSite at the same time?
You'll need to make a simple registry change to allow this. The registry key may vary a little by what version of Homesite you are using.

Find: HKEY_CURRENT_USER\Software\Macromedia\HomeSite5
Add (string value): allowMultipleInstances = -1

Tip: Learn to Check and Read the References
There are an incredible number of sites, articles, books and people willing to tell you how to do things on the internet, especially in webdesign. Unfortunately, not all of them are accurate. You must learn, not only how to test assertions yourself, but also how to RTFM. (Read The Friendly Manuals) There really *are* definitive resources out there that have the correct answers to many questions. Steve Champeon's Webmonkey article, RTFM: A Guide to Online Research is a great start, encouraging people to actually read and check the definitive references and teaching them how. This goes for ASP, HomeSite and for any technology.
FAQ: Are there any "Built with HomeSite" button images?
Allaire had made a couple several years ago. Here are copies. Keep in mind that few websites put on this type of buttons anymore. Up to you. If you use these, COPY THEM TO YOUR OWN SITE. DO NOT JUST LINK TO THE IMAGE COPIES ON MY SITE. If I find people doing that I'll have to replace the images with something you won't like on your page... ;-)

Or you may prefer just an icon logo image. Here are 2 from HomeSite version 5, and 2 from version 5.5.

img/icon_hs.gif img/icon_hs_sm.gif img/icon_hs_55b.gif img/icon_hs_55.gif

And, from Taylor McKnight's Steal These Buttons (developed category) is this blog-size button.

img/lk_homesite_sm.gif