Abstract: Systems and methods for using private keys in software development that minimizes the risks of the private key being lost or stolen. A strong name consists of the assembly's identity, e.g., its simple text name, version number, and culture information (if provided), plus a public key and a digital signature. It is generated from an assembly file using the corresponding private key. The private/public key pair is persisting in a password-encrypted file using a standard encryption format that can be made available to everyone. The first time any subsystem of the development environment requires use of the private key contained in an encrypted file format, the developer is prompted to provide the password to decrypt the key. The user supplies the password and the public/private key is imported into a non-exportable key container in the local cryptographic store.

Abstract: To package an application and a component to be available for use in connection with the application into a package, a type of the package and a location where the package is to be stored are received, as is a selection of the component to be packaged with the application. For the selected component, at least one packaging-specific object in such component is referred to to determine information on how to package the component in the package and/or how to install the component on the computing device of the user.

Abstract: A system and method that allows developers to debug a component while it is restricted by any arbitrary set of specific permissions, or restricted by an existing permission set associated with a security “zone.” A security sandbox is mimicked within the development environment so that developers can study how applications perform inside the sandbox. Developers are able create any sandbox and debug inside it, where violating any bound of the artificial sandbox will throw a security exception and drop the user out on the exact line of code which generated the error, as well as provide helpful information about how to correct the error.

Abstract: An error/exception helper may provide tailored help when an error such as an exception is generated. A source program editor interface may be displayed and/or focus given to the program editor interface. An error/exception bubble or tool tip may be displayed, which, in one embodiment of the invention, points to the line of code that generated the exception. The error/exception bubble may include a link to a help topic or the actual help text may be displayed within the bubble. The bubble may also include one or more actions that may be taken to correct the error or a link to a procedure to perform the action(s). The source code may be edited, actions initiated and execution re-initiated at which time the bubble and editor interface display may be dismissed.

Abstract: An error/exception helper may provide tailored help when an error such as an exception is generated. A source program editor interface may be displayed and/or focus given to the program editor interface. An error/exception bubble or tool tip may be displayed, which, in one embodiment of the invention, points to the line of code that generated the exception. The error/exception bubble may include a link to a help topic or the actual help text may be displayed within the bubble. The bubble may also include one or more actions that may be taken to correct the error or a link to a procedure to perform the action(s). The source code may be edited, actions initiated and execution re-initiated at which time the bubble and editor interface display may be dismissed.