LosaDev source snapshot 2019

extra/LS_Service/LS_launcher/ReadMe.txt

@@ -0,0 +1,93 @@
+================================================================================
+    MICROSOFT FOUNDATION CLASS LIBRARY : LS_launcher Project Overview
+===============================================================================
+
+The application wizard has created this LS_launcher application for 
+you.  This application not only demonstrates the basics of using the Microsoft 
+Foundation Classes but is also a starting point for writing your application.
+
+This file contains a summary of what you will find in each of the files that
+make up your LS_launcher application.
+
+LS_launcher.vcproj
+    This is the main project file for VC++ projects generated using an application wizard. 
+    It contains information about the version of Visual C++ that generated the file, and 
+    information about the platforms, configurations, and project features selected with the
+    application wizard.
+
+LS_launcher.h
+    This is the main header file for the application.  It includes other
+    project specific headers (including Resource.h) and declares the
+    CLS_LauncherApp application class.
+
+LS_launcher.cpp
+    This is the main application source file that contains the application
+    class CLS_LauncherApp.
+
+LS_launcher.rc
+    This is a listing of all of the Microsoft Windows resources that the
+    program uses.  It includes the icons, bitmaps, and cursors that are stored
+    in the RES subdirectory.  This file can be directly edited in Microsoft
+    Visual C++. Your project resources are in 1033.
+
+res\LS_launcher.ico
+    This is an icon file, which is used as the application's icon.  This
+    icon is included by the main resource file LS_launcher.rc.
+
+res\LS_launcher.rc2
+    This file contains resources that are not edited by Microsoft 
+    Visual C++. You should place all resources not editable by
+    the resource editor in this file.
+
+
+/////////////////////////////////////////////////////////////////////////////
+
+The application wizard creates one dialog class:
+
+LS_launcherDlg.h, LS_launcherDlg.cpp - the dialog
+    These files contain your CLS_launcherDlg class.  This class defines
+    the behavior of your application's main dialog.  The dialog's template is
+    in LS_launcher.rc, which can be edited in Microsoft Visual C++.
+
+
+/////////////////////////////////////////////////////////////////////////////
+
+Other Features:
+
+ActiveX Controls
+    The application includes support to use ActiveX controls.
+
+/////////////////////////////////////////////////////////////////////////////
+
+Other standard files:
+
+StdAfx.h, StdAfx.cpp
+    These files are used to build a precompiled header (PCH) file
+    named LS_launcher.pch and a precompiled types file named StdAfx.obj.
+
+Resource.h
+    This is the standard header file, which defines new resource IDs.
+    Microsoft Visual C++ reads and updates this file.
+
+LS_launcher.manifest
+	Application manifest files are used by Windows XP to describe an applications 
+	dependency on specific versions of Side-by-Side assemblies. The loader uses this 
+	information to load the appropriate assembly from the assembly cache or private 
+	from the application. The Application manifest  maybe included for redistribution 
+	as an external .manifest file that is installed in the same folder as the application 
+	executable or it may be included in the executable in the form of a resource. 
+/////////////////////////////////////////////////////////////////////////////
+
+Other notes:
+
+The application wizard uses "TODO:" to indicate parts of the source code you
+should add to or customize.
+
+If your application uses MFC in a shared DLL, you will need 
+to redistribute the MFC DLLs. If your application is in a language 
+other than the operating system's locale, you will also have to 
+redistribute the corresponding localized resources MFC80XXX.DLL. 
+For more information on both of these topics, please see the section on 
+redistributing Visual C++ applications in MSDN documentation. 
+
+/////////////////////////////////////////////////////////////////////////////