IPWorks Zip Avis

Response to berandor [USA] >This is due to their using the .net licensing model. It took me a while to find their documentation on how to get the job done and then only with very careful attention to what needed to be put into the licenses.licx file was I successful. I would think they would post a working example Yes, by default we use the .Net licensing scheme (as do many other components), but we also provide an alternative method. I'm sorry that it took you a while to find the documentation detailing how to work with the .Net licensing model, but it is posted on our knowledge base. Also, as for a demo showing how to deal with the licx file - ALL of the demo projects that install with IP*Works! ZIP show this. >I don't like to be limited to installation using setup projects as I am working within a corporation where I can easily xcopy my projects to where they need to go. I'm not sure what you mean by this - you do not have to run a setup in order to deploy your project to a server. There is no problem with using XCOPY deployment of any projects whether they contain IP*Works! ZIP components or not. >For me the biggest problem is that v6.0 does not handle files that exceed 4 gigabytes. Apparently this has been resolved in version 7.0 but nSoftware will only send v7.0 to people with a subscription. IP*Works! ZIP V7 is a new product. Yes, one of the benefits of being a subscription customer is that you have access to new products before they are available to the public. I'm not sure why you would call this "shameless", since we're doing this as a service to our subscription customers. FInally, I find it odd that you give a 2-star rating to a product that you say "is relatively easy to use" especially since you apparently got it working after finding the answers to the problems you encountered (with the .net licensing, not our component) on our website.

This component is relatively easy to use. Implementation is somewhat more difficult when deploying to a non-developer machine. This is due to their using the .net licensing model. It took me a while to find their documentation on how to get the job done and then only with very careful attention to what needed to be put into the licenses.licx file was I successful. I would think they would post a working example and draw your attention to this as most devs are going to care about it. I don't like to be limited to installation using setup projects as I am working within a corporation where I can easily xcopy my projects to where they need to go. For me the biggest problem is that v6.0 does not handle files that exceed 4 gigabytes. Apparently this has been resolved in version 7.0 but nSoftware will only send v7.0 to people with a subscription. (difference of about $1200 per seat). You cannot purchase it under the single developer license. This is a very annoying practice. I recommend you find something else, these guys are shameless.