|Prerequisite: .NET Framework 2.0, you can download it from Microsoft's site
1. Download binary from this link and unpack it anywhere on your disk (.exe and .config file must remain together)
2. Double click on WordAutoSaver.exe to start the program
3. Select monitor directory - directory where you save your word files. DO NOT select root directory (C:\\ or D:\\ or any other) but rather go deeper into structure (C:\\Documents is OK)
4. Select archive directory - where your files will be archived. Again - DO NOT select root directory
5. 'Save files from last x minutes' setting allows you to influence how often backup process will be triggered. If you select 10 minutes, than your file will be backed-up every 10 minutes
6. 'Send (CTRL+S)', your file will not be backed up if it hasn't changed in that, previously mentioned, 10 minute period. If you are one of those persons that forgets to Save their document, check this box and WordAutoSaver will send CTRL+S for you every time before starting the backup of file (kinda like AutoSave).
7. 'Delete files older than x minutes', you of course do not wish to keep backup files in archives for too long (after all you are saving them in your normal directory) which can be influenced with this setting - default is 2 days (2 * 24 * 60).
Couple settings that are not exposed in UI (they are embedded in config file):
-MonitorFilter1: filter used for finding files to backup in MonitorDir
-MonitorFilter2: another field if you wish another file type
-MonitorProcessName: name of process (in your TaskManager) that you want to target for sending CTRL+S
(You can change these settings to MonitorFilter1: *.xls, MonitorProcessName: EXCEL, in order to have same AutoSave functionality for Excel)
-StartMinimized: if you want to have WordAutoSaver start with Windows (by coping shortcut to it into Start Menu -> Startup), you'll probably want to start it minimized (replace False with True)
That's it. Leave comments/contact me if you run into any kind of problems.
*Utility is dedicated to my friend Stephen Vizinczey -> http://stephenvizinczey.com/
%d, %i signed int
%u unsigned int
%x, %X hexadecimal int
%o octal int
%e float/double (in scientific notation)
%g float/double (as %f or %e, depending on value)
%s C string (bytes)
%S C string (unichar)
%.*s Pascal string (requires two arguments, pass pstr as the first, pstr+1 as the second)
%lld long long
%llu unsigned long long
%Lf long double
|Bah... this proved tougher than I originally thought, because all I could find were bunch of smart-ass comments that contained no code. You'll hopefully evade that path by following these steps:
1. Download Solution from -> http://www.sendspace.com/file/465sb6[^]
2. Open .sln, press F5 -> press Button -> you should get dialog with bunch of variables showing that server is aware of calling client's credentials and culture
3. Open SilverlightWcf/Page.xaml.cs to see how calls are initialized - note that you only set culture/username/password during proxy's creation.
How to import this into your solution? Easy:
1. Copy Util.CustomHeader.Silverlight & Util.CustomHeader.WcfService projects into your solution's folder
2. Reference Util.CustomHeaders.Silverlight from your Silverlight project, Util.CustomHeaders.WcfService from your WCF project
3. Decorate your WCF service with [CustomHeadersBehaviorAttribute] attribute (alternatively you can set this in config by using CustomHeadersBehavior, see ref #3 for more details)
4. Add reference to your WCF service from Silverlight project and after proxy class generation is finished you'll use code like this to initialize your service:
ClientChannelBinding binding = new ClientChannelBinding();
ClientChannelBinding.Culture = "sr-Latn-CS";
ClientChannelBinding.Username = "username";
ClientChannelBinding.Password = "password";
EndpointAddress endpoint = new EndpointAddress(
client = new SilverlightWcf.ServiceReference1.Service1Client(binding, endpoint);
client.GetDataCompleted += client_GetDataCompleted;
private ServiceReference1.Service1Client client;
Of course, I recommend that you create some kind of WebServiceFactory.cs in your Silverlight project that will create services for you and do this initialization... while also exposing that web service URI in some config.
For those interested in details of how this works:
#1 - http://fluffyidentity.blogspot.com/2008/08/custom-wcf-channel-in-silverlight.html[^]
#2 - http://geekswithblogs.net/SunnyCoder/archive/2009/03/15/username-password-amp-ws-security-with-silverlight.aspx[^]
#3 - http://weblogs.asp.net/paolopia/archive/2007/08/23/writing-a-wcf-message-inspector.aspx[^]
|OK, I played a bit more. Here are my suggestions so far:
1) When asking for insurance, use a themed popup, rather than the standard message box. It seems out of place (and the beep it does drives me nuts).
2) When asking for insurance, change the buttons to read "Yes" and "No" rather than "OK" and "Cancel"
I played about a hundred hands - everything seems to work fine.