Fixed Travis CI build status link to use this forked repo instead of the original one
Added VisualStudio11 configuration and new configurations debug-noboost-dll + release-noboost-dll

Note: Up to now, the build has only be made run and tested for the stuff we need for our product, i.e.
 - Only the new configurations debug-noboost-dll + release-noboost-dll
 - Only with 64Bit
 - Only assimp and assimpview
Merge pull request #2 from AIM360/AddVisualStudio11Config

Added VisualStudio11 configuration and made it build for no-boost-dll config and 64Bit
3DSLoader: Skipped chunks of size 0
ColladaLoader: Added unit conversion to meters
Added UTF8-support on windows for DefaultIOSystem::Exists() method
DefaultIOStream::FileSize(): Replaced windows-based version to use mFile directly instead of fileStat

Unfortunately, it is not 100% clear anymore what's the background of this change. Maybe it was faster or it avoided issues in case that file loaders used exclusive open.
All I know is that this change is not the accidental result of a merge, because according to SVN blame, this code section had never been touched since revision 1. So it must have been done for InfraWorks for some reason.
So I preserved this change to avoid regression due to the AssImp update.
Delete assimp.sdf

It was accidentally submitted
Merge pull request #4 from AIM360/AddVisualStudio11Config

Delete assimp.sdf
Added some VisualStudio-generated files to Git-ignore
Added simple batch file for automatic build of AssImp for InfraWorks

Obviously it only works for Windows platforms with VS2012. It would be cleaner to do it with CMake for all Platforms.
But this would require some more work and is not necessary as long as we don't use AssImp on other Platforms.
Activated pdb generation in AssImp projects

(for the projects configurations that we are using in InfraWorks)
Merge pull request #3 from AIM360/OldInfraWorksFixes

Applied old InfraWorks patches to current AssImp
Made open method work for UTF8 paths on windows
SortByPType Posprocessing crashed for crappy models with degenerated geometry

Which models crashed before the fix?:
The crash was observed for files with the following properties:
1. They contain >=1 meshes
2. They were loaded with SortByPType option
3. They only contained degenerated meshes, so that these were skipped SortByPType

What is improved by the fix?:
Obviously, the affected models were crappy anyway and will still produce empty output after the fix. However, the fix avoids the heap-corruption, which couldn't be solved by try/catch from outside and had the annoying effect that a whole scene with hundreds of individual models could crash due to a single crappy one.

Why did it crash before?
The SortByPType deleted some exluded meshes, but didn't reset the pointers in pScene. After throwing the DeadlyImportException (no remaining meshes), remaining meshes were deleted => Excluded meshes were deleted twice.
Incrased PATHLIMIT value for Windows platforms in order to support extended paths

(see code comments for details)
Merge pull request #5 from AIM360/PathIssueFixes

Path issue fixes
Merge pull request #6 from AIM360/FixedCrashForDegenerateObjFiles

Fixed crash for degenerate obj files
Activated Multiprocessor compile option (/MP) for AssImp projects

This makes build time significantly shorter.
Fixed VS11 solution config for static AssImp builds (no effect on InfraWorks): Some static 64-Bit solution configs refered to 32-Bit project configs