Does the Method-level encryption technique offer additional benefits in terms of licensing?
Yes, actually it does. For the first time, developers of .NET applications can license and control their applications at the Method level. This means that they can treat individual methods as they would any other features they define with SRM. So, for example, you could separately license features that save to different file types, even if the individual Methods the application used were all included under the same .NET Class. So, in addition to HASP SRM v 2.50 providing unmatched protection for .NET fr 2.0 and 3.0 applications, what other new functionality can software vendors expect with this new version? Actually, there are quite a few things. I’ll just quickly run through the list for you: • We’ve added a new Business Studio Server API so that HASP SRM license generation and tracking can now be connected to ERP / CRM systems to generate orders, produce updates (V2Cs) and produce Product Keys. • A license expiration notification now allows the Business Studio Server to send notifica
