Scanning receipts from iPhone to OneNote (App Store)

There are many ways to scan a document, such as a receipt, and import it into OneNote. I’m now using the App Store version of OneNote on Windows10 and one of the (many) limiations is the inability to resize large images without having to cut them out, edit, and paste back in.

I’ve tried a bunch of scanning apps on the iPhone and one of the main issues is finding something than can scan, including auto-detection of document borders, adjust brightness and contrast, and send to OneNote. The Adobe Scanner app for the iPhone is awesome but the PDF appears in OneNote as an icon and doesn’t appear to want to change into a readable document!

So for now the fastest way I’ve found is to use the Microsoft Office Lens iPhone app – this does a great job of scanning and although I can’t change the image resolution I can set it as a simple black and white image and send directly to OneNote.

First, run Office Lens.

1

 

Then let it find your document – it helps to have some natural contrast between the edges of the document and the background. 

Make sure that the Document option is selected:

Display the filters after scanning the document – just slide your finger up to view them:

I’m choosing the black and white option as it seems to help keep the file size down and also makes the receipt more readable:

After applying the filter click on the Done button at the bottom and go through the export options:

Enter a title for the note and choose which section on OneNote to save it to:

 

It would be a great improvement if the Office Lens app could have a quality or file size option to reduce the amount of data stored in ON. There are already suggestions for this on the Office Lens feedback hub going back to 2015 – not sure if anyone’s listening tho!

Advertisements

Visual Studio 2013 to 2015, MSB3884, Could not find rule set file

After loading a VS2013 C# project in VS2015 I got the dreaded MSB3884 warning (Could not find rule set file). A little annoying since I wasn’t knowingly using code analysis (but I might now).

Here’s what I did to fix the warning:

  1. On the project properties go to the Code Analysis section.
  2. Select the Browse option on the list of rule sets:
    W10_Test.png
  3. Browse to the VS2015 rule sets folder:
    C:\Program Files (x86)\Microsoft Visual Studio 14.0\Team Tools\Static Analysis Tools\Rule Sets
  4. Pick a rule set.. the default used by new projects is:
    MinimumRecommendedRules.ruleset
  5. The new rule set is applied:
    W10_Test.png

Then rebuild – problems gone !