.NET
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
*Tim Riley
Demand Loading Issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
96 Views, 4 Replies
07-27-2005 06:30 AM
I was just wondering how everyone is dealing with demand loading .dll's for
multiple versions of AutoCAD. Basically I want to create an installer that
will work for either AutoCAD Mechanical 2005 or the version of Mechanical
2005 that comes with Inventor. My problem is they reside under different
registry keys, ACAD-305:409 and ACAD-303:409. Is there an easier way other
than checking to see if these registry keys exist and then installing? What
if I wanted to distribute this to people whom I didn't know what vertical
flavor of AutoCAD they were using?
I haven't started working on my NSIS script yet but when I do I'd like to
know if there's an easier option for me.
TIA,
Tim Riley
multiple versions of AutoCAD. Basically I want to create an installer that
will work for either AutoCAD Mechanical 2005 or the version of Mechanical
2005 that comes with Inventor. My problem is they reside under different
registry keys, ACAD-305:409 and ACAD-303:409. Is there an easier way other
than checking to see if these registry keys exist and then installing? What
if I wanted to distribute this to people whom I didn't know what vertical
flavor of AutoCAD they were using?
I haven't started working on my NSIS script yet but when I do I'd like to
know if there's an easier option for me.
TIA,
Tim Riley
*Laurie Comerford
Re: Demand Loading Issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-27-2005 04:20 PM in reply to:
*Tim Riley
Hi Tim,
I use Inno Setup to do the installs. I would strongly suggest that you use
this as your install program if you are not already doing so.
I can check for installed versions of AutoCAD with script as follows:
function R2006LandFound(): Boolean;
begin
if RegKeyExists( HKLM, 'SOFTWARE\Autodesk\AutoCAD\R16.2\ACAD-4008:409')
then begin
Result := true;
end
else
begin
Result := false;
end;
end;
I have a file "CADAppsFindVersions.txt" containing this (and all the others
versions of AutoCAD relevant for our products) and I attach this file to all
installation scripts as follows:
[Code]
#include "C:\Installation\CADApps Install
Items\InnoSetupStdScripts\CADAppsFindVersions.txt"
Then the scripts from this file are used as follows:
[Files]
Source: {src}\Programs\Landscape-2006-v5.dvb; DestDir:
{app}\Landscape\Programs; Flags: external ignoreversion; Check:
R2006LandFound
If Land Desktop 2006 is not installed then the line above is not invoked
based on the output returned to 'Check' by the function 'R2006LandFound'
Laurie Comerford
CADApps
www.cadapps.com.au
"Tim Riley" wrote in message
news:4912244@discussion.autodesk.com...
I was just wondering how everyone is dealing with demand loading .dll's for
multiple versions of AutoCAD. Basically I want to create an installer that
will work for either AutoCAD Mechanical 2005 or the version of Mechanical
2005 that comes with Inventor. My problem is they reside under different
registry keys, ACAD-305:409 and ACAD-303:409. Is there an easier way other
than checking to see if these registry keys exist and then installing? What
if I wanted to distribute this to people whom I didn't know what vertical
flavor of AutoCAD they were using?
I haven't started working on my NSIS script yet but when I do I'd like to
know if there's an easier option for me.
TIA,
Tim Riley
I use Inno Setup to do the installs. I would strongly suggest that you use
this as your install program if you are not already doing so.
I can check for installed versions of AutoCAD with script as follows:
function R2006LandFound(): Boolean;
begin
if RegKeyExists( HKLM, 'SOFTWARE\Autodesk\AutoCAD\R16.2\ACAD-4008:409')
then begin
Result := true;
end
else
begin
Result := false;
end;
end;
I have a file "CADAppsFindVersions.txt" containing this (and all the others
versions of AutoCAD relevant for our products) and I attach this file to all
installation scripts as follows:
[Code]
#include "C:\Installation\CADApps Install
Items\InnoSetupStdScripts\CADAppsFindVersions.txt"
Then the scripts from this file are used as follows:
[Files]
Source: {src}\Programs\Landscape-2006-v5.dvb; DestDir:
{app}\Landscape\Programs; Flags: external ignoreversion; Check:
R2006LandFound
If Land Desktop 2006 is not installed then the line above is not invoked
based on the output returned to 'Check' by the function 'R2006LandFound'
Laurie Comerford
CADApps
www.cadapps.com.au
"Tim Riley"
news:4912244@discussion.autodesk.com...
I was just wondering how everyone is dealing with demand loading .dll's for
multiple versions of AutoCAD. Basically I want to create an installer that
will work for either AutoCAD Mechanical 2005 or the version of Mechanical
2005 that comes with Inventor. My problem is they reside under different
registry keys, ACAD-305:409 and ACAD-303:409. Is there an easier way other
than checking to see if these registry keys exist and then installing? What
if I wanted to distribute this to people whom I didn't know what vertical
flavor of AutoCAD they were using?
I haven't started working on my NSIS script yet but when I do I'd like to
know if there's an easier option for me.
TIA,
Tim Riley
*Tony Tanzillo
Re: Demand Loading Issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-27-2005 08:18 PM in reply to:
*Tim Riley
"Laurie Comerford" wrote
>>>
function R2006LandFound(): Boolean;
begin
if RegKeyExists( HKLM, 'SOFTWARE\Autodesk\AutoCAD\R16.2\ACAD-4008:409')
then begin
Result := true;
end
else
begin
Result := false;
end;
end;
<<<<
Yes, except that the above can be distilled down to this:
Function R2006LandInstalled: Boolean;
begin
Result := RegKeyExists( HKLM, 'SOFTWARE\Autodesk\... blah blah");
end;
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
>>>
function R2006LandFound(): Boolean;
begin
if RegKeyExists( HKLM, 'SOFTWARE\Autodesk\AutoCAD\R16.2\ACAD-4008:409')
then begin
Result := true;
end
else
begin
Result := false;
end;
end;
<<<<
Yes, except that the above can be distilled down to this:
Function R2006LandInstalled: Boolean;
begin
Result := RegKeyExists( HKLM, 'SOFTWARE\Autodesk\... blah blah");
end;
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
*Laurie Comerford
Re: Demand Loading Issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-27-2005 08:26 PM in reply to:
*Tim Riley
Hi Tony,
Thanks. That makes complete sense.
All my pascal script is based on "minimal understanding - semi-guesswork -
trial and error" till it works - then leave alone.
Yes, except that the above can be distilled down to this:
Function R2006LandInstalled: Boolean;
begin
Result := RegKeyExists( HKLM, 'SOFTWARE\Autodesk\... blah blah");
end;
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
--
Laurie Comerford
CADApps
www.cadapps.com.au
Thanks. That makes complete sense.
All my pascal script is based on "minimal understanding - semi-guesswork -
trial and error" till it works - then leave alone.
Yes, except that the above can be distilled down to this:
Function R2006LandInstalled: Boolean;
begin
Result := RegKeyExists( HKLM, 'SOFTWARE\Autodesk\... blah blah");
end;
--
http://www.caddzone.com
AcadXTabs: MDI Document Tabs for AutoCAD 2004/2005/2006
http://www.acadxtabs.com
--
Laurie Comerford
CADApps
www.cadapps.com.au
*Tim Riley
Re: Demand Loading Issues.
Options
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
07-28-2005 07:14 AM in reply to:
*Tim Riley
Laurie:
Thanks I'll check out Inno Setup.
Tim Riley
"Laurie Comerford" wrote in message
news:4913033@discussion.autodesk.com...
Hi Tim,
I use Inno Setup to do the installs. I would strongly suggest that you use
this as your install program if you are not already doing so.
I can check for installed versions of AutoCAD with script as follows:
function R2006LandFound(): Boolean;
begin
if RegKeyExists( HKLM, 'SOFTWARE\Autodesk\AutoCAD\R16.2\ACAD-4008:409')
then begin
Result := true;
end
else
begin
Result := false;
end;
end;
I have a file "CADAppsFindVersions.txt" containing this (and all the others
versions of AutoCAD relevant for our products) and I attach this file to all
installation scripts as follows:
[Code]
#include "C:\Installation\CADApps Install
Items\InnoSetupStdScripts\CADAppsFindVersions.txt"
Then the scripts from this file are used as follows:
[Files]
Source: {src}\Programs\Landscape-2006-v5.dvb; DestDir:
{app}\Landscape\Programs; Flags: external ignoreversion; Check:
R2006LandFound
If Land Desktop 2006 is not installed then the line above is not invoked
based on the output returned to 'Check' by the function 'R2006LandFound'
Laurie Comerford
CADApps
www.cadapps.com.au
"Tim Riley" wrote in message
news:4912244@discussion.autodesk.com...
I was just wondering how everyone is dealing with demand loading .dll's for
multiple versions of AutoCAD. Basically I want to create an installer that
will work for either AutoCAD Mechanical 2005 or the version of Mechanical
2005 that comes with Inventor. My problem is they reside under different
registry keys, ACAD-305:409 and ACAD-303:409. Is there an easier way other
than checking to see if these registry keys exist and then installing? What
if I wanted to distribute this to people whom I didn't know what vertical
flavor of AutoCAD they were using?
I haven't started working on my NSIS script yet but when I do I'd like to
know if there's an easier option for me.
TIA,
Tim Riley
Thanks I'll check out Inno Setup.
Tim Riley
"Laurie Comerford"
news:4913033@discussion.autodesk.com...
Hi Tim,
I use Inno Setup to do the installs. I would strongly suggest that you use
this as your install program if you are not already doing so.
I can check for installed versions of AutoCAD with script as follows:
function R2006LandFound(): Boolean;
begin
if RegKeyExists( HKLM, 'SOFTWARE\Autodesk\AutoCAD\R16.2\ACAD-4008:409')
then begin
Result := true;
end
else
begin
Result := false;
end;
end;
I have a file "CADAppsFindVersions.txt" containing this (and all the others
versions of AutoCAD relevant for our products) and I attach this file to all
installation scripts as follows:
[Code]
#include "C:\Installation\CADApps Install
Items\InnoSetupStdScripts\CADAppsFindVersions.txt"
Then the scripts from this file are used as follows:
[Files]
Source: {src}\Programs\Landscape-2006-v5.dvb; DestDir:
{app}\Landscape\Programs; Flags: external ignoreversion; Check:
R2006LandFound
If Land Desktop 2006 is not installed then the line above is not invoked
based on the output returned to 'Check' by the function 'R2006LandFound'
Laurie Comerford
CADApps
www.cadapps.com.au
"Tim Riley"
news:4912244@discussion.autodesk.com...
I was just wondering how everyone is dealing with demand loading .dll's for
multiple versions of AutoCAD. Basically I want to create an installer that
will work for either AutoCAD Mechanical 2005 or the version of Mechanical
2005 that comes with Inventor. My problem is they reside under different
registry keys, ACAD-305:409 and ACAD-303:409. Is there an easier way other
than checking to see if these registry keys exist and then installing? What
if I wanted to distribute this to people whom I didn't know what vertical
flavor of AutoCAD they were using?
I haven't started working on my NSIS script yet but when I do I'd like to
know if there's an easier option for me.
TIA,
Tim Riley
