Multiple StartUp Suites For Same Version of AutoCAD 2010 (Profiles?)

[lamensterms]

Hey guys,

 

At work we used the addon ProSteel program with AutoCAD 2010, and depending on which particular client we are working for at the time… we either use ProSteel Version 3 or Version 4. ProSteel Version 3 and 4 are not compatible with each other – but they both run on AutoCAD 2010.

 

We use Command Line Switches in 2 different AutoCAD shortcuts to launch each version of ProSteel.

 

The problem I am having is… with each version of ProSteel we use… we have a specific set out LISP routines to run with that version. For example, the LISP routine we use to insert dimensions on ProSteel 3 is not the same routine as we use on ProSteel 4.

 

So I was just wondering if it is at all possible to have a different set of LISP routines run (or a separate Startup Suite) depending on how we start our AutoCAD/ProSteel session (either use profiles or the command line switch).

 

I hope that explanation was clear enough.

 

Thanks so much for any help.

[dbroada]

I am sure there are better ways but this may be worth considering.

 

You can use the /p switch in your shortcut to load different profiles. Each profile can have a different set of search paths. You could have all your common lisp files in a combined folder but have the version dependant LISP files in two other folders, only one of which is included in each profile.

[RobDraw]

Having two shortcuts with a different /p switch for each was the first thing that came to my mind, too. Although, I don't think having different search paths is necessary. The key is the Startup Suite(s). Having different profiles allows you to load different lisps for each.

[lamensterms]

Hi guys,

 

Thanks for the replies. I thought the separate profiles would have been a good place to start. But I did do a little experimenting with profiles and the startup suite.. and I could not get the startup suite to be profile dependant. The startup suite was consistent regardless of which profile I had set at the time.

 

Is that normal? Any idea how I could have unique startup suites for each profile?

 

Thanks again.

[BlackBox]

To echo what's already been said, I too highly recommend using Profiles.

 

As for Startup Suite, I respectfully depart from my friends, and instead recommend using an Acad.lsp and/or AcadDoc.lsp file for each Profile. As on who no longer uses Startup Suite, I could not be certain as to where it stores it's information, but presumably that is the Registry.

 

Cheers

[lamensterms]

Hi BlackBox,

 

Thanks for taking the time to reply.

 

So you suggest creating 2 Acad.lsp and/or AcadDoc.lsp files in 2 seperate directories? 1 for ProSteel 3 and 1 for ProSteel 4. Then I just modify the "Support File Search Path" in each of the ProSteel 3/4 profiles to point to the appropriate Acad.lsp?

 

Thanks again.

[RobDraw]

I did not know that the start-up suite would be persistent between profiles. It sounds like you have a good plan. Let us know how it works out.

[BlackBox]

Thanks for taking the time to reply.

 

You're very welcome.

 

So you suggest creating 2 Acad.lsp and/or AcadDoc.lsp files in 2 seperate directories? 1 for ProSteel 3 and 1 for ProSteel 4. Then I just modify the "Support File Search Path" in each of the ProSteel 3/4 profiles to point to the appropriate Acad.lsp?

 

All I can do is offer what has worked well for us... If you find value in that as it might apply to your situation, that's great.

 

Essentially, our support structure is scaleable by design to allow for new versions being implemented. Inherently we add a 'Common' area where things that are not version-specific reside. As for our SFSP, while we obviously require some local install paths (especially using verticals), most of our SFSP is on the network, where part is read-only to most, and the remainder is personal network space where only that user has access. The former is where we keep enterprise support files, and the latter is where users keep their customizations which is also mapped into our setup for ease of use.

 

As a result of our support structure, it's easy to keep the Acad.lsp, and AcadDoc.lsp files organized as well, as these are considered to be version-specific resources, and located accordingly.

 

So as an example path for Acad.lsp, and AcadDoc.lsp in one of our Profile's SFSP:

 

SomeDrive:\\SomePath\\2012\\C3D\\LISP\\

 

... Managing the Profile via Acad.lsp is as simple as replacing \\2012\\ with \\2014\\ in various places, such as my call to vla-Put-SupportPath, etc., and everything else falls into place for the new Profile.

 

Replicate, and refine. Lemon squeezy.

Edited May 2, 2013 by BlackBox

[BlackBox]

I thought an image might help with the example provided; see my previous post.

[lamensterms]

Hi BlackBox and Rob,

 

Thanks again for your help. Seems like a pretty logical system, I havent had time to try it out but I think it should work exactly as I need. I intend to duplicate our existing Acad.LSP file, put each in specific directories for each ProSteel version, and add a unique line at the end of each file to call another lisp routing which loads the relevant LISP routines for each version of ProSteel.

 

I will let you know how I go.

 

Thanks again.