We have a project which is deployed to Windows, WindowsCE, iOS, and now soon to be Android. We have near 98% code re-use.
For all other platforms, we put all of our static images, sound files, etc, into subfolders inside a folder called "_Resources".
For example, we have "_Resources/Images/..." is where we put all of our UI images.
We place all of our .csproj files side by side, such as this: {ProjectName}.Windows.csproj {ProjectName}.iPad.csproj {ProjectName}.Droid.csproj
And this is how we achieve our 98% easy code re-use.
But Droid is adding a strange requirement. In order for our Resource files to be "Copied to Output Folder", they MUST be put into "Assets/" folder??? Is this true? Is there no way around it?
It sure would be nice if we could have Xamarin studio deploy our "_Resources" folder as is, right into the same folder where it deploys our assemblies.
On all other platforms, we achieve this filesystem scheme:
{AppFolder}/ ./{ProjectName}.exe ./{ProjectDep}.dll ./_Resources/.... <<== all of our resources should be copied here
Is there any way to make Droid deployment work in this fashion? Otherwise, we're going to let the "tail wag the dog" and change our whole file system over to comply with Droid's very peculiar requirement (of using "Assets/" folder).
I just can't image why this "Assets/" folder must be a hardcoded name. Why is it not configurable? And why doesn't Droid respect my settings on resource files when I set it to "Content" and "Copy to Output Folder". That should "just work", shouldn't it?