| Dart Home | PowerTCP Sockets for .NET | Custom Development | Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
| Author | Forum: PowerTCP Sockets for .NET (Secure and Standard) Topic: Distribution |
| mcanaday From: Lincoln, NE USA Posts: 6 Member Since: 08/27/02 |
posted November 6, 2002 6:01 PM I have a question about distribution of the PowerTCP SSL Sockets for .NET (that's a mouthful). I have a communications DLL that I have compiled that contains the component. I also have a licenses.licx file. For distribution do I just give my DLL and the licenses file to the customer or do they need a dartsock.dll? In the old version of the TCP client, you needed to distribute the Dartsock.dll to the client and register it in the system directory. I am not sure how this will work in .NET. Do I have a Dartsock DLL to distribute with my app or is the licenses file sufficient? I noticed in another post where you mention looking at the distribution section in the help file. In the help file that I have, there is not a section on distribution. I downloaded the newest MSI file today to be sure I had the latest version. Any help always apprecaited. Matt. |
Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted November 6, 2002 7:22 PM The licx is NOT distributed. That's used during compilation. When you compile the app, the output directory should contain a copy of all the files you need. Also, if you create a setup project with the setup wizard, it will detect what you need. |
| mcanaday From: Lincoln, NE USA Posts: 6 Member Since: 08/27/02 |
posted November 7, 2002 11:01 AM OK. I don't distribute the licenses.licx file to my end customers. However, I think that any program that calls my communications DLL needs to have the licenses.licx file. So if other developers are writing applications that would invoke my communications DLL, then any application they create that would call the communications DLL would need the licenses.licx file. Is this correct? When I created the setup package for my communications dll, I did notice that it added the dart.powertcp.sslsockets.dll. I am guessing this is the dll that I need to distribute. I would prefer not to have a separate setup package for my communications dll, but rather have the individual applications package all necessary files. Thanks for your input, as always it is extremely helpful! |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted November 7, 2002 11:28 AM If someone uses your DLL to develop an app, they will have to own a copy of the same product that you own, so they would just add to the licx for their app. Just to reiterate, if your customer uses your DLL to develop something, your customer will have to buy the SslSockets product as well as your product. |
| mcanaday From: Lincoln, NE USA Posts: 6 Member Since: 08/27/02 |
posted November 7, 2002 5:23 PM Just one more stab at clarity, and I will try to re-focus my question. I develop a communications program (A.DLL). We have a site license for development of applications using SSLSockets for .NET. A different developer creates an application (B.EXE). This B.EXE will be distributed to our clients (end-users). When they distribute B.EXE as an MSI package, I just want to be sure we have everything included. I am assuming that the package for B.EXE will include A.DLL as well as the dart.powertcp.sslsockets.dll. This is the primary question: Do I need to package the sslsockets dll with the final package or will it work without it? I think I have already learned that B.EXE needs to have a licenses.licx file, but once compiled, the licenses.licx file does NOT need to be included in the MSI package for the client (end-user). Hopefully I am being clearer this time. I know that I could just start loading this up on a clean PC and testing it, but I was hoping for some wisdom before-hand. Thanks again for your time. |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted November 7, 2002 5:39 PM You will always have to deliver the Sockets DLL. Anything that uses it will always need it. Microsoft seems to waver on the ways to distribute, but they seem to recommend having the DLL be in the same directory that uses it. They also mention the GAC (Global Assembly Cache) but to be honest I don't see the need. For info on the GAC you'll have to do your own research via newsgroups or directly from MS. The licx file is associated with a project. It is not something you distribute. The guy who writes B.EXE will add A.DLL as a reference. This will automatically add all the DLL's that A.DLL references. If he already has a licx in his project he needs to add the lines that are in yours to his. If he doesn't have one he can use the same one you use. By the way, if you have a site license you don't need to waste time posting here as I think you have the right to phone support included. |
K M Drake From: Utica, NY USA Posts: 3406 Member Since: 07/14/00 |
posted November 8, 2002 9:06 AM Hi, So as to not mislead you, if you purchased Priority Support for the product you have a Site License for, you have phone support. But it is not included with the price of the Site License. -ken |
| pcolton From: Rancho Santa Fe, CA USA Posts: 1 Member Since: 02/18/03 |
posted February 18, 2003 2:05 PM So an .exe is the only type of distributable that I can deliver under the license? That is, if I have a .dll that implements a library that uses the PowerTCP classes, my customer can't use it without getting their own license? Even if this library doesn't expose the PowerTCP classes? |
| K M Drake From: Utica, NY USA Posts: 3406 Member Since: 07/14/00 |
posted February 18, 2003 5:09 PM Hi, You can create a dll that uses our components, and use this dll to construct applications, as long as the application developer has a license for our Tool (for example, yourself). You cannot, however, use our Tool to create a dll for other, non-licensed developers to use in their apps. -ken |
| blevan From: elgin, IL USA Posts: 6 Member Since: 03/12/03 |
posted March 30, 2004 1:10 PM I have question that i am having issue with SSL Socket DLL. We develope a dll that has reference of Scoket Dll, which i am referencing our applicantion. When ever i run the project and excute the the form that references the ddll, i get a error telling me that Dart.PowerTCP is not registered. I look at the licenses.licx file and line is in the file, but it doesn't work. As always thak you for your help in this issue. |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted March 30, 2004 1:17 PM If you create a DLL that uses our DLL, any project that uses your DLL will need to have the same info in it's own licenses.licx. The person using your DLL will also need to purchase PowerTCP. |
| blevan From: elgin, IL USA Posts: 6 Member Since: 03/12/03 |
posted March 30, 2004 1:24 PM Our primary application now needs to use a component developed using the SslSockets Component. Of 10 developers, only 2 actually handle the component that uses the SslSockets Component. Is there no way we can directly include our component in the primary application short of buying 8 more licenses? |
| Tony Priest From: Utica, NY USA Posts: 8466 Member Since: 04/11/00 |
posted March 30, 2004 1:30 PM Not that I know of. Anyone who compiles your app will need a license. I would suggest contacting us directly to discuss options. Please call 315-790-5456 or write to sales@dart.com |
| Reply | PowerTCP Sockets for .NET (Secure and Standard) Topics | Forums |
This site is powered by
PowerTCP WebServer for ActiveX
|