I'm about to develop an aplication for Windows Phone, and I'll use an external paid library (some of the Aspose products). As many of You know, the license file for their libraries are applied on each application execution. But, if I put that project in the Windows Store, how to secure the license file from being stolen ? Because it'll be included in that project.
To apply license file as an embedded resource, add the license file to your project and set it's "Build Action" property as "Embedded Resource", after this you can use following code to apply license:
// Create a PDF license object
Aspose.Pdf.License license = new Aspose.Pdf.License();
// Instantiate license file
license.SetLicense("Aspose.Total.lic");
// Set the value to indicate that license will be embedded in the application
license.Embedded = true;
For further details, please have a look at the "Embedding the License as a Resource" article in Aspose.Pdf documentation.
As far as use of Aspose libraries in a Windows Phone application is concerned, it has not been announced yet if Aspose libraries are fully compatible with Windows Phone platform or not. Good thing is that the verified/tested Aspose product libraries for Windows Phone platform should be available for use very soon and then you can use them without any issues.
My name is Iqbal and I am developer evangelist at Aspose.
Related
Hello, I am developing a program for my company.
In this project, we need to implement a feature that previews zebra's zpl in C#.
Therefore, I want to use an external library (Nuget), but the famous Labelary not only has restrictions on continuous use, but the company does not want security information to be passed on.
Therefore, I want to use a Nuget package called Binary Kits, but this package also seemed to support how to use Labelary and its own viewer module.
If I use Binary Kits' own viewer module, I wonder if there will be any problems such as my data being
transferred to another place, or there being a limit on the number of preview uses.
enter image description here
I installed BinaryKits.Zpl.Viewer and these packages were downloaded automatically.
I have converted my Win32 app written with C/C++/MFC into a UWP app using Desktop Bridge. The app will be published in the store under trial license. I found this code that illustrates how to check for trial license, its expiration, etc using StoreAppLicense class.
My issue is how to test it?
My app is built in the older version of VS that did not have a concept of the Windows Store.
My issue is how to test it
There are two namespaces related to IAP function: Windows.Services.Store and Windows.ApplicationModel.Store.
If use the Windows.ApplicationModel.Store namespace, these apps can use the CurrentAppSimulator class to simulate license info during testing. See In-app purchases and trials using the Windows.ApplicationModel.Store namespace
While the Windows.Services.Store namespace doesn't have a class to do so.
Please see the testing guidance
The Windows.Services.Store namespace does not provide a class that you can use to simulate license info during testing. Instead, you must publish an app to the Store and download that app to your development device to use its license for testing. This is a different experience from apps that use the Windows.ApplicationModel.Store namespace, as these apps can use the CurrentAppSimulator class to simulate license info during testing
(Update 10/21/2016)
I'm not clear about your development device sentence though. The app is developed on a Windows 8.1 device and is uploaded via a Chrome browser
That sentence is quoted from this document
It means we need to convert the Win32 application to Converted UWP app and upload to the Store first, even though we have not implemented the IAP function.
Is there a way to manually associate an app with a Windows desktop?
Sure, please see Create your app by reserving a name
Here is a screenshot of App identity of a uwp app on the Windows Dev Center
Note, please fill this form if you need to upload a Converted UWP app: LINK
This request needs several business days to get response.
I am quite confused as to the proper way of distributing Bonjour as a part of a Windows application that would publish a service for a client iOS app.
No matter how much I google around, I cannot find a clear how-to guide. It would be great if someone could provide guidelines.
The main reasons of my confusion are:
Is it mandatory to distribute the entire bonjour Win SDK as a part of my Win application?
Since Apple provides source code to build mDNSResponder.exe, is it sufficient to only distribute such file along with dns-sd.dll?
What is the intended purpose of providing sources for mDNSResponder.exe otherwise?
What is the recommended way to handle the possibility of having Bonjour already installed on the system?
Also, where can I find the latest Bonjour SDK (3.x I guess?), I can only find 2.0.4. Is it only accessible if I am enrolled in the OSX developer program? (I am enrolled in iOS developer program for now.)
Many thanks.
This is information I gathered from various sources, including communications with official Apple support. I report it in the way I believe to be accurate, I hope it can be useful (no liability assumed!).
For Bonjour-enabled Windows application you have basically two main options:
Bundle the Bonjour Installer with your application (which is not the Bonjour SDK, the SDK if for your own developer use only).
If you choose to do so, the Bonjour installer must be called from your own installer during the installation process. The possibility of Bonjour being already installed in the system is totally handled by the Bonjour installer.
And here come some bad news: you must include de Bonjour Logo on your physical distribution medium (like a DVD cover sleeve) according to the Apple guidelines specified in the Windows Bundling Agreement, and you need Apple approval before distributing your product.
Do not bundle. I.e., do not distribute Bonjour with your application but simply use it if already present in the system. If you do not distribute Bonjour in any form the whole Windows Bundling Agreement simply does not apply. You application should search for the dnssd.dll and load it dynamically if found.
Consider that most of Windows users would have Bonjour already installed due to the fact that some popular apps use it (for example iTunes and Skype).
While the source code of Bonjour is released under an open-source library (Apache License, Version 2.0) this does not require Apple to do anything. In particular, they do not need to document how you'd use this license.
The license allows you to use and adapt Apple's source code, including its copyright, but not including its trademark "Bonjour(TM)". Since this is the standard Apache license, you don't have the requirement either to show the trademark.
So, to answer your questions:
No, you can build your own version of Bonjour from source and use that under the Apache license. You can't call it Bonjour, but why do you need a name in the first place? "mDNS" would be a reasonable choice, possibly prefixed with your trademark.
It seems sufficient to distribute the DLL and EXE. Arranging how they find each other might benefit from some tailoring, so your own build of Bonjour doesn't clash with Apple's.
(I won't speculate on Apple's motives)
The design problem here is that Bonjour acts as a system service, and services are inherently singletons. If you install it unmodified, Apple wouldn't be able to install its own build. That's not a legal problem, probably, but it is a bad customer experience. Installing your own build as a distinct service would avoid the clash, allowing both versions to co-exist.
(Resource request, off-topic)
Can I use google code prettify for commercial use. I see that Code license - Apache License 2.0. Do I need to have a copy of the Apache license?
Google Code Prettify is published under Apache License 2.0. Take a look to this FAQ. It allows you to use Apache software in packages or distributions that you create.
However you need to include a copy of license in any distribution of your software and show clear attribution to Google.
Google Code Prettify is distributed under Apache Licence 2.0.
This means that you are free to use it in a commercial application provided that you also include a copy of the Apache License with your application.
RELATED: https://stackoverflow.com/a/1007376/2081889
I would like to implement/use-existing a cross platform configuration settings tool like about:config in Firefox. It would have to work on Windows and Mac. Are there any libraries or design patterns out there that people recommend?
Also, if I were to use a library, it would have to be "free as in beer" and couldn't be a GPL license. The apache license would be ok.
The Windows side uses C++/MFC and the Mac side uses Objective-C. The configuration file would have to be read on both platforms, but they don't have to share the same library.
Properties files/ini files.
Python has a library. (Config Parser)
C++ probably quite a few, but this is a top google hit. (RudeConfig)
Java has ini4j
.NET has nini