Cake integration

[jzeferino]

Add cake to call the code and create two projects to simulate android and ios.

[jzeferino]

@luisgoncalves checkin in.

[luisgoncalves]

In order to use the #r directive we need to already have the assembly on disk. This means that on the final solution we have two options:

• Invoke Cake "after build"
• Make the converter a CLI and invoke it directly

[luisgoncalves]

Oh nevermind. The assembly with the converter will come from a package, so it will be available before build.

[jzeferino]

Yep!

[jzeferino]

Should we change the ResxParser to library instead of executable?

[luisgoncalves]

Do you want to stick to Cake or just use this from the command-line? You'll probably already have Cake in place for the project, but just invoking the EXE "after build" would be mush faster.. Not sure what's the best option :)

We could include both a DLL and an EXE on the NuGet package, but that's probably overkill.

[jzeferino]

Since we will have to take care and test the EXE in windows/osx (guess it will run out of the box, but...) it will be better to have the DLL only.

Im creating another console project just to RUN the DLL, for debug and development purposes. Seems good?

[jzeferino]

Did full project renaming and added new project only for mobile converters. Take a look and tell if it makes more sense than before.

[luisgoncalves]

The project rename looks good. However, we can't have the #r and usage of the converter (RunResxConverter task) on the same Cake file as the build because the assembly won't exist on the first place. Unless we can add assembly reference dynamically.

[jzeferino]

The build.cake that we have now is just a runner for the test the .dll. Guess the best option now isto refactor that build.cake to build/run tests/generate artifacts.

Will do that soon.

Another important note (maybe we need to create a issue for it) is that we will need to call the code form ResxConverter.Mobile.dll before building a .csproj containing the .resx