Welcome to Telelogic Product Support
  Home Downloads Knowledgebase Case Tracking Licensing Help Telelogic Passport
Telelogic DOORS (steve huntington)
Decrease font size
Increase font size
Topic Title: Best Practice for giving users access to addins, including Wexp?
Topic Summary: where to store addins and Wexp so that all users get access?
Created On: 22-May-2008 19:45
Status: Post and Reply
Linear : Threading : Single : Branch
Search Topic Search Topic
Topic Tools Topic Tools
Quick Reply Quick Reply
Subscribe to this topic Subscribe to this topic
E-mail this topic to someone. E-mail this topic
Bookmark this topic Bookmark this topic
View similar topics View similar topics
View topic in raw text format. Print this topic.
 22-May-2008 19:45
User is offline View Users Profile Print this message


Joseph Dubin

Posts: 26
Joined: 1-Mar-2006

We're using Wexp V11.5 with DOORS V8.1.

Question: What's the best practice for giving users access to addins generally, and Wexp specifically?

Right now our approach is that we store it on a file server on the network, in an addins folder (addins\WEXP). DOORS clients use -a \\<network-drive-path>\addins

They also have their DOORS shortcut "Start in" directory set to \\<network-drive-path>\ one level above the addins directory. Otherwise, Wexp gives an error when started: -E- DXL: <Line:1> could not open include file (addins/WEXP/include/wexpload.inc) (No such file or directory)

Is there a downside to setting the start directory to a network drive or accessing addins on a network drive?

-------------------------
Joseph DUBIN
joseph.dubinNOSPAM@freescale.com
Freescale Semiconductor, Inc.
Report this to a Moderator Report this to a Moderator
 12-Jun-2008 14:44
User is offline View Users Profile Print this message


Kevin Murphy

Posts: 120
Joined: 16-Jan-2008

I do not know of a downside to using "Start in", but I want to tell you that I believe you are using the best approach for addins.

When I put WEXP on the network for my users, I just edit the path to the wexpload.inc to match what it is on the network, instead of using the relative path.

-------------------------
Kevin Murphy
http://www.baselinesinc.com
Report this to a Moderator Report this to a Moderator
 27-Jun-2008 22:10
User is offline View Users Profile Print this message


Joseph Dubin

Posts: 26
Joined: 1-Mar-2006

Kevin,

Thanks for the feedback.

I did edit the path to wexpload.inc. When I did, wexpload.inc loaded, but it then tries to load something else which also has a relative path:

-E- DXL: <[...]addins/WEXP/include/wexpload.inc:9> could not open include file (addins/WEXP/include/global.inc) (No such file or directory)
Included from:
<Line:1>

And unfortunately, wexpload.inc is encrypted so I can't edit it. :-( So I'll have to stick with the "start in" directory being set to the network path.

-------------------------
Joseph DUBIN
joseph.dubinNOSPAM@freescale.com
Freescale Semiconductor, Inc.
Report this to a Moderator Report this to a Moderator
Statistics
20925 users are registered to the Telelogic DOORS forum.
There are currently 1 users logged in.
The most users ever online was 15 on 15-Jan-2009 at 16:36.
There are currently 0 guests browsing this forum, which makes a total of 1 users using this forum.
You have posted 0 messages to this forum. 0 overall.

FuseTalk Standard Edition v3.2 - © 1999-2009 FuseTalk Inc. All rights reserved.