| Author |
Message |
Tim Riley
Guest
|
 Posted:
Wed Mar 30, 2005 7:21 pm Post subject:
.NET Assemblies Legal Issues. |
|
|
When I compile a type library in Visual C# it copies all of the assemblies I
reference into the /bin/release/ folder. I am assuming it does this so I can
zip this whole directory, distribute it and the user will have all the files
required to run my program within that directory.
Now my question is am I legally allowed to distribute these files? Say I'm
working on a community project, can I post a zip including the binary files
acdbmgd.dll and acmgd.dll on a website? Otherwise I am going to have to
develop some sort of install script that either builds the project from
source.
TIA,
Tim Riley
|
|
| Back to top |
|
 |
Mike Tuersley
Guest
|
| Posted:
Wed Mar 30, 2005 7:45 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
For the references, set the Local Copy property to false then they won't be
copied local.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon... |
|
| Back to top |
|
|
Tim Riley
Guest
|
| Posted:
Wed Mar 30, 2005 9:19 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Mike:
Thanks for the info. But how then do the end users use my dll? When I
referenced acdbmgd.dll and acmgd.dll I had to manually select them at the
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
match?
Tim Riley
"Mike Tuersley" <mtuersley_NOT_@rand.com> wrote in message
news:y1vgwh7uz1kl$.1hs4i3yh09bhx.dlg@40tude.net...
| Quote: | For the references, set the Local Copy property to false then they won't
be
copied local.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon... |
|
|
| Back to top |
|
|
Paul Richardson
Guest
|
| Posted:
Wed Mar 30, 2005 11:33 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
| Quote: | path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
|
Tim,
I was just reading about this in a C# standards manual for Classes. The
author was adamant about not hard coding any paths in your classes. For
just this reason. I would obtain the version and location from the local
computer. Otherwise Try Catch? I'm not the expert here.
gl
Paul
"Tim Riley" <riltim______at_____gmail.com> wrote in message
news:424ad1ab$1_1@newsprd01...
| Quote: | Mike:
Thanks for the info. But how then do the end users use my dll? When I
referenced acdbmgd.dll and acmgd.dll I had to manually select them at the
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
match?
Tim Riley
"Mike Tuersley" <mtuersley_NOT_@rand.com> wrote in message
news:y1vgwh7uz1kl$.1hs4i3yh09bhx.dlg@40tude.net...
For the references, set the Local Copy property to false then they won't
be
copied local.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
|
|
|
| Back to top |
|
|
Frank Oquendo
Guest
|
| Posted:
Wed Mar 30, 2005 11:44 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Tim Riley wrote:
| Quote: | Now my question is am I legally allowed to distribute these files?
|
I don't see why not. .NET makes it very easy to install assemblies which
are to be referenced from the GAC. Autodesk didn't go that route so
either it's an oversight or a design choice. |
|
| Back to top |
|
|
Tim Riley
Guest
|
| Posted:
Thu Mar 31, 2005 12:11 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Paul:
I'm not hardcoding any paths. The References required to access AutoCAD from
..NET are not available in the normal .NET GAC I have to click the browse tab
and add them manually. It is beyond me how I could find these .NET
assemblies automatically.
Tim Riley
"Paul Richardson" <noSPAM@nospam.com> wrote in message
news:424af0d8$1_3@newsprd01...
| Quote: | path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
Tim,
I was just reading about this in a C# standards manual for Classes. The
author was adamant about not hard coding any paths in your classes. For
just this reason. I would obtain the version and location from the local
computer. Otherwise Try Catch? I'm not the expert here.
gl
Paul
"Tim Riley" <riltim______at_____gmail.com> wrote in message
news:424ad1ab$1_1@newsprd01...
Mike:
Thanks for the info. But how then do the end users use my dll? When I
referenced acdbmgd.dll and acmgd.dll I had to manually select them at the
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
match?
Tim Riley
"Mike Tuersley" <mtuersley_NOT_@rand.com> wrote in message
news:y1vgwh7uz1kl$.1hs4i3yh09bhx.dlg@40tude.net...
For the references, set the Local Copy property to false then they won't
be
copied local.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
|
|
|
| Back to top |
|
|
Tim Riley
Guest
|
| Posted:
Thu Mar 31, 2005 12:17 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Very true. I'm still a little nervous as the last thing I need is Autodesk
coming after me because I made their proprietary files available to pre-2005
people.
Tim Riley
"Frank Oquendo" <foquendo@gmail.com> wrote in message
news:424af38a$1_3@newsprd01...
| Quote: | Tim Riley wrote:
Now my question is am I legally allowed to distribute these files?
I don't see why not. .NET makes it very easy to install assemblies which
are to be referenced from the GAC. Autodesk didn't go that route so either
it's an oversight or a design choice.
|
|
|
| Back to top |
|
|
Norman Yuan
Guest
|
| Posted:
Thu Mar 31, 2005 1:19 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
When you set reference in .NET app to COM base app (Acad), a .NET interop
wrpper .DLL file is created (or you use PIA provided by the COM App
manufacturer). I think you are free to send these Interop .Dll assemblies to
your user. However, in the case of AutoCAD, I doubt you can legally send the
COM dll that wrpped by the Interop. dll. On the other hand, if your users
have the same AutoCAD product installed, they do not need these COM dll
file. If they do not have the same AutoCAD product, your .NET app will not
work, even you give them those COM dll files.
File location is irrelevant: the com dlls are registered with Windows
registry, the Interop dll wrapper uses Registry to locate COM dll.
"Tim Riley" <riltim______at_____gmail.com> wrote in message
news:424af9ee$1_3@newsprd01...
| Quote: | Paul:
I'm not hardcoding any paths. The References required to access AutoCAD
from
.NET are not available in the normal .NET GAC I have to click the browse
tab
and add them manually. It is beyond me how I could find these .NET
assemblies automatically.
Tim Riley
"Paul Richardson" <noSPAM@nospam.com> wrote in message
news:424af0d8$1_3@newsprd01...
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
Tim,
I was just reading about this in a C# standards manual for Classes. The
author was adamant about not hard coding any paths in your classes. For
just this reason. I would obtain the version and location from the local
computer. Otherwise Try Catch? I'm not the expert here.
gl
Paul
"Tim Riley" <riltim______at_____gmail.com> wrote in message
news:424ad1ab$1_1@newsprd01...
Mike:
Thanks for the info. But how then do the end users use my dll? When I
referenced acdbmgd.dll and acmgd.dll I had to manually select them at
the
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
match?
Tim Riley
"Mike Tuersley" <mtuersley_NOT_@rand.com> wrote in message
news:y1vgwh7uz1kl$.1hs4i3yh09bhx.dlg@40tude.net...
For the references, set the Local Copy property to false then they
won't
be
copied local.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
|
|
|
| Back to top |
|
|
Tim Riley
Guest
|
| Posted:
Thu Mar 31, 2005 1:55 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Norman:
I am not using COM at all, only AutoCAD's .NET API (acdmgd.dll and
acmgd.dll).
Tim Riley
"Norman Yuan" <NotReal@NotReal.not> wrote in message
news:424b09c9$1_3@newsprd01...
| Quote: | When you set reference in .NET app to COM base app (Acad), a .NET interop
wrpper .DLL file is created (or you use PIA provided by the COM App
manufacturer). I think you are free to send these Interop .Dll assemblies
to
your user. However, in the case of AutoCAD, I doubt you can legally send
the
COM dll that wrpped by the Interop. dll. On the other hand, if your users
have the same AutoCAD product installed, they do not need these COM dll
file. If they do not have the same AutoCAD product, your .NET app will not
work, even you give them those COM dll files.
File location is irrelevant: the com dlls are registered with Windows
registry, the Interop dll wrapper uses Registry to locate COM dll.
"Tim Riley" <riltim______at_____gmail.com> wrote in message
news:424af9ee$1_3@newsprd01...
Paul:
I'm not hardcoding any paths. The References required to access AutoCAD
from
.NET are not available in the normal .NET GAC I have to click the browse
tab
and add them manually. It is beyond me how I could find these .NET
assemblies automatically.
Tim Riley
"Paul Richardson" <noSPAM@nospam.com> wrote in message
news:424af0d8$1_3@newsprd01...
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
Tim,
I was just reading about this in a C# standards manual for Classes. The
author was adamant about not hard coding any paths in your classes. For
just this reason. I would obtain the version and location from the
local
computer. Otherwise Try Catch? I'm not the expert here.
gl
Paul
"Tim Riley" <riltim______at_____gmail.com> wrote in message
news:424ad1ab$1_1@newsprd01...
Mike:
Thanks for the info. But how then do the end users use my dll? When I
referenced acdbmgd.dll and acmgd.dll I had to manually select them at
the
path "c:\program files\autodesk\acadm 2005\". Does this mean that if I
release my dll and the end user is using AutoCAD 2005 but not AutoCAD
Mechanical 2005 that the program will not work because the paths don't
match?
Tim Riley
"Mike Tuersley" <mtuersley_NOT_@rand.com> wrote in message
news:y1vgwh7uz1kl$.1hs4i3yh09bhx.dlg@40tude.net...
For the references, set the Local Copy property to false then they
won't
be
copied local.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon...
|
|
|
| Back to top |
|
|
Mike Tuersley
Guest
|
| Posted:
Thu Mar 31, 2005 3:48 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
net dll don't need published, signed, or strong named to be used, only if
you want them in the GAC. I never do that with mine, either.
For 2005, Adesk strong named their dlls so you need to provide a copy of
the ones you are using and create an acad.exe.config file with binding
redirects if you are using different versions than those already installed
- i.e. you wrote in vanilla acad, enduser has mechanical.
If you are writing to 2006, don't use the local copy and you don't need to
send the dlls. Strong names are gone in 2006 and 2006 is set to handle
adjusting to the appropriate dll version.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon... |
|
| Back to top |
|
|
Mike Tuersley
Guest
|
| Posted:
Thu Mar 31, 2005 3:53 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
On Wed, 30 Mar 2005 12:44:30 -0600, Frank Oquendo wrote:
| Quote: | Tim Riley wrote:
I don't see why not. .NET makes it very easy to install assemblies which
are to be referenced from the GAC. Autodesk didn't go that route so
either it's an oversight or a design choice.
I'd say both =) |
Oversight -
For 2005, Adesk strong named their dlls so you need to provide a copy of
the ones you are using and create an acad.exe.config file with binding
redirects if you are using different versions than those already installed
- i.e. you wrote in vanilla acad, end user has mechanical. It'd look
something like this:
<configuration>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="acmgd" publicKeyToken="7208edf2a10162b1"
culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535"
newVersion="16.1.84.0" />
</dependentAssembly>
<dependentAssembly>
<assemblyIdentity name="acdbmgd" publicKeyToken="7208edf2a10162b1"
culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-65535.65535.65535.65535"
newVersion="16.1.84.0" />
</dependentAssembly>
</assemblyBinding>
</runtime>
<startup>
<!--Adesk always uses the latest version of the framework installed on the
computer. If youare having problems then explicitly specify the framework
version. For example, to specify .NET 1.1 uncomment the following line.
<supportedRuntime version="v1.1.4322"/>
-->
</startup>
</configuration>
Design choice -
If you are writing to 2006, don't use the local copy and you don't need to
send the dlls. Strong names are gone in 2006 and 2006 is set to handle
adjusting to the appropriate dll version.
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon... |
|
| Back to top |
|
|
Mike Tuersley
Guest
|
| Posted:
Thu Mar 31, 2005 4:10 am Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Oh, I should add that I don't strong name my dlls because they are not
exposed to COM - otherwise I would
-- Mike
___________________________
Mike Tuersley
___________________________
the trick is to realize that there is no spoon... |
|
| Back to top |
|
|
Frank Oquendo
Guest
|
| Posted:
Thu Mar 31, 2005 8:34 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Mike Tuersley wrote:
| Quote: | Oh, I should add that I don't strong name my dlls because they are not
exposed to COM - otherwise I would
|
Isn't strong naming required for COM components? |
|
| Back to top |
|
|
Tim Riley
Guest
|
| Posted:
Thu Mar 31, 2005 8:38 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
He said he's not using COM so he doesn't have to strong name.
Tim Riley
"Frank Oquendo" <foquendo@gmail.com> wrote in message
news:424c1884$1_3@newsprd01...
| Quote: | Mike Tuersley wrote:
Oh, I should add that I don't strong name my dlls because they are not
exposed to COM - otherwise I would
Isn't strong naming required for COM components?
|
|
|
| Back to top |
|
|
Frank Oquendo
Guest
|
| Posted:
Thu Mar 31, 2005 8:42 pm Post subject:
Re: .NET Assemblies Legal Issues. |
|
|
Tim Riley wrote:
| Quote: | He said he's not using COM so he doesn't have to strong name.
|
That's not what I asked. His comments imply that strong naming is
optional so I'm checking my memory to make sure it's still functioning
correctly. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in