I’d like to take a closer look at the use of CodeMaps in Visual Studio to debug and to document our solution. The following link to Architecture and Modeling has some very cool videos detailing how to use Code Maps to find the root cause of a bug. Further to debugging Code Maps can be used to assist in documenting program flow and dependency chains visually. Lets start with a very basic example of how to generate a CodeMap. First off if you don’t know what a Code Map is then let me explain. When browsing your VS project files and looking at the ‘References’ link that appears above a method declaration, if you pay careful attention you’ll see the link ‘Show on Code Map’. See below. Read more
What is Software Licensing?
Software licenses typically provide users with the right to one or more copies of the software without violating copyrights. The license also defines the responsibilities of the parties entering into the license agreement and may impose restrictions on how the software can be used. Software licensing terms and conditions usually include the usages of the software, warranties and disclaimers and protections if the software or its use infringes on the intellectual property rights of others.
About Rhino Licensing –
Rhino Licensing uses Public-key cryptography, also known as asymmetric cryptography, it’s a class of cryptographic algorithms which requires two separate keys, one of which is secret (or private) and one of which is public. Although different, the two parts of this key pair are mathematically linked. The public key is used to encrypt plaintext or to verify a digital signature; whereas the private key is used to decrypt cipher text or to create a digital signature. The term “asymmetric” stems from the use of different keys to perform these opposite functions, each the inverse of the other – as contrasted with conventional (“symmetric”) cryptography which relies on the same key to perform both. You encrypt a value using the one key, and it can only be decrypted using the other key. In the case of license key generation, we store our private key on the server, and distribute the public key with our application. When the user receives a license key, the application is able to verify that it came from us by using the public key. If someone tampers with the license key it will be invalid and the software will no longer execute.
Cloud computing allows development teams to get applications into production faster. ITSM leaders must adopt new strategies and change existing processes or risk becoming a bottleneck.
Successful cloud computing requires the DevOps — the fusion of development and operations with the goal of accelerating time to market and reducing time to value. The good news is that ITIL is uniquely positioned to accelerate DevOps — but it requires changes to existing ITSM processes. In this session Hank Marquis will show you:
– How to tune and tweak ITIL processes to shift your operations into high gear and make sure your organization benefits from cloud computing
– The ways cloud changes business, and how IT has to respond to remain relevant
– The changes existing ITSM/ITIL processes require to avoid becoming a bottleneck
– How ITIL is uniquely positioned to facilitate DevOps