Mini Application Blocks Code
Status: Alpha
Brought to you by:
foozinator
File | Date | Author | Commit |
---|---|---|---|
BootStrap | 2007-09-14 | foozinator | [r2] - Moved Auto Update projects into a folder to m... |
ErrorHandler | 2008-02-28 | Foozinator | [r3] Fixed the Updater HttpTransport |
Library | 2007-09-08 | foozinator | [r1] Initial Check-in. |
ManifestGenerator | 2007-09-14 | foozinator | [r2] - Moved Auto Update projects into a folder to m... |
Updater | 2008-02-28 | Foozinator | [r3] Fixed the Updater HttpTransport |
MiniAppBlocks.sln | 2007-09-14 | foozinator | [r2] - Moved Auto Update projects into a folder to m... |
ReadMe.txt | 2007-09-08 | foozinator | [r1] Initial Check-in. |
Mini Application Blocks Read Me ================================ The purpose of this project is to provide low-overhead solutions to common application problems. /* ***** BEGIN LICENSE BLOCK ***** * Version: MPL 1.1/GPL 2.0/LGPL 2.1 * * The contents of this file are subject to the Mozilla Public License Version * 1.1 (the "License"); you may not use this file except in compliance with * the License. You may obtain a copy of the License at * http://www.mozilla.org/MPL/ * * Software distributed under the License is distributed on an "AS IS" basis, * WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License * for the specific language governing rights and limitations under the * License. * * The Original Code is Micro Assembly Blocks Assembly Info. * * The Initial Developer of the Original Code is * Andrew Searls. * Portions created by the Initial Developer are Copyright (C) 2007 * the Initial Developer. All Rights Reserved. * * Contributors: * Andrew Searls (foozinator@gmail.com) * * Alternatively, the contents of this file may be used under the terms of * either the GNU General Public License Version 2 or later (the "GPL"), or * the GNU Lesser General Public License Version 2.1 or later (the "LGPL"), * in which case the provisions of the GPL or the LGPL are applicable instead * of those above. If you wish to allow use of your version of this file only * under the terms of either the GPL or the LGPL, and not to allow others to * use your version of this file under the terms of the MPL, indicate your * decision by deleting the provisions above and replace them with the notice * and other provisions required by the GPL or the LGPL. If you do not delete * the provisions above, a recipient may use your version of this file under * the terms of any one of the MPL, the GPL or the LGPL. * * ***** END LICENSE BLOCK ***** */ Contents: * ErrorHandler - Adopted from Jeff Atwood's Visual Basic application error handling code. ( Coding Horror mention: http://www.codinghorror.com/blog/archives/000102.html sample VB code available http://www.codeproject.com/dotnet/ExceptionHandling.asp ) Use: 1. Set the appropriate values in your .exe project app.config. (The updater application is a good reference for settings) 2. Reference this assembly and call UnhandledExceptionManager.AddHandler(). 3. Where the application can handle an exception gracefully, call one of the HandledExceptionManager.ShowDialog overloads. * Updater - ManifestGenerator - Simple auto-update bootstrap. Builds and consumes a manifest and distribution package used to keep installations up to date. NOTE: This is a simple deployment engine and does not offer much protection from corruption. There is no warranty or guarantee against someone placing a virus in the deployment package. Use: 1. Create a production build of your application. The only files in the directory should be files to be deployed. 2. Start ManifestGenerator and point it to the application .exe file. It will list all the files in the directory and all subdirectories. 3. Check any files that could be included in a partial update (from the previous deployment version only). 4. Click the "Load Previous Manifest" to load the last deployment manifest. (optional step, ignore for initial deployment). 5. Click "Save". There will be a new manifest and deployment files in the ManifestGenerator directory. 6. Move the manifest and deployment files to a server that is accessible by the intended clients. 7. Change the Updater app.config to point to the manifest file on the aforementioned server. 8. Deploy the Updater app for all initial installations. 9. Running the Updater app will check the manifest, download an update if necessary, then start the main app.