When I start working on a SalesLogix web project I do a few things to make my life a little easier. Hopefully these steps will help make your experience a bit better.
1. Create a root development project folder for the client
Every client gets their own root folder that will contain all of work that I need to complete. I put this on a local drive.
2. Create a blank file based VFS for the project.
I do not start in the Database any more since I want to make sure that the customizations are completely isolated out of the SalesLogix database. This makes it easier to store in source code.
3. Import a project into the blank VFS.
I never export out of the Database VFS. I always start with a baseline project backup.
4. Make sure that everything compiles correctly and can be deployed.
I will not put the file based VFS into source control until I have confirmed that it does work. If there is any repair work, or I need to reload the project its better to do it before it is in SCC then when it is not
5. Put the VFS in source control.
6. Create a Visual studio .Net Class Project.
This project will be located within the root development folder. The reason to locate them closely is that when you are adding support files the browser opens up to the location of the VFS. If they are close in proximity it is easier to find the assemblies to load into. I try to do most of my mainline coding in the assembly. It allows the reuse of some assets and allows for a better development experience including grouping of all of the source code into a central location. If your using Visual Studio 2008 it also allows for the usage of better constructs.
7. Create a Libraries folder
Your .Net class file will need to reference core assemblies. Creating a library folder under the root will allow you to put the common assemblies need to build your code in one location. This way if you move your project or provide it to someone all of the required build artifacts are easily located. It may be advisable to create a batch file to copy the assemblies from a source location like the deployment bin folder into your library directory in case you need to refresh some of the assemblies (Sage.Entity.Interfaces, …)
7. Add a asset folder for all of the artifacts (documents, images and the like)
8. Make sure everything is checked into Source code control.
I would not check in the library files as they can be regenerated as needed.
If the File based VFS cannot be located when Application Architect is opened it is possible that you will get a fault. So if you are using swappable or USB drives to store your project files on and they are not currently docked this could be a cause of problems. Keep that in mind as the project loading functionality is not quite fortified.