I tried copying my .AddIn file to the AllUsers path one time, and it worked.  Also, there is another folder where the add-in can load from, and that's the [My Documents]\Visual Studio 2005\AddIns folder.  If you drop the .AddIn file in there, it should load as well.

Thanks Trent. It might be worth while to add the "add-in" info the the installation doc (Unless it's already there and I missed it. Wouldn't be the first time)

-Larry

Yes, we will probably add this functionality back.  We took it out because we had so many people fail to install the database which caused a number of support issues.

Everything would be fine EXCEPT the add-in file since Visual Studio expects this on a per user basis.  You can simply copy the add-in file over to any other user and then menu should then appear.  Below is the default path to the add-in folder:

I have a few installation issues.

It would seem that the logical way to set up SF in a team environment would be to use a common SF database so that multiple developers cold work on the same project. It would be nice if the installation process we're smart enough to realize that the SF and Sample databases were already updated to the current level. In our environment the SQL database is located across a WAN making each install a 30+ minute process while the demo data is loaded.

While installing StrataFrame the installation process encountered an error while trying to deploy the StrataFrame metadata. This may be due to the fact that an install was running on another PC. Should the install process handle concurrency when there are multiple installs running that share the same SF and sample database?

When StrataFrame is installed should it be useable by anyone that logs on to the PC or only to the user that installed it? After installing SF successfully under one user ID the StrataFrame menu was not visible to another user that logged in to the same PC. The templates were there but the SF menu in Visual Studio was missing.

-Larry