Digital Code signing binaries such as exes, dlls , scripts by the software supplier not only identifies the source of the software but also asserts authenticity.
Digital Code signing is usually done as part of the build process where binaries are digitally signed as they are built.
However this can impose overhead and add complexities in development build environments.
An ideal solution would be to do digital signing as a separate step during nightly production builds that unpackages binaries from MSI, CAB, Zip files;digitally sign them and repackage back.
Often times software, data files etc. needs to be packaged and sent across. Zip files are sufficient in most cases. However, sometimes complex deployment needs could arise. For example, multiple versions, operations on the files, folders before copy and after copy etc.
Easy Installer Creator provides an easy MSI based solution.
Troubleshooting production issues of an older release is daunting due to non availability of symbols and source code. Symbol Server and Source Indexing technogies make it seamless to debug.
Source Indexing enables downloading source code from source control during debugging in Visual Studio. This is very helpful while debugging production issues of older releases. The current Source Indexing setup from Microsoft doesn't support RTC repository. Writing the same in Perl seems complicated for those unfamiliar with Perl.
RTC repository Source Indexer enables Source indexing RTC Repositories seamlessly.
In the diversified development environment of today, multiple code repositories are used by cross development teams. As each have an indigenous way to deal with patches, a generic method of creating and applying patches is much desired along with recursive folder comparison and viewing the file differences and other operations. The portable patch tool attempts to address.
In many development environments, updating outdated Installers of the development tools can be challenging as the original development environment used for generating the installer will be no longer available.
In such cases, an installer can be disassembled, changes be applied and reassembled back using MS installer APIs.
During a project's life cycle, moving the code base to the next version of visual studio becomes necessary to take advantage of newer features.
This can be daunting task if there are a large number of projects.
Visual Migration Helper utility makes it a breeze.
No comments:
Post a Comment