[Mono-ue] A call to establish a C# / Mono development and build environment for the plugin

David Ford davidfordaus at gmail.com
Thu Mar 19 21:58:18 UTC 2015

I think my request still stands.  There is very little (if any) benefit to
having each individual developer compiling on their own.  Few (if any)
Unreal downloadable examples appear to use 4.4.

I am re-tasking our developers to Unity as of this morning, and halting
Unreal development entirely.   We may return to Unreal at some point, but
will review the decision to support two engines in detail before committing
to that effort.

If there are someone within Xamarin / Unreal that this email can be
forwarded to - I'd appreciate it.  We're expending effort developing
products, not wasting time recompiling (with compilation errors, as it
turns out) non-production grade toolchains.



On 20 March 2015 at 03:24, Ali Scissons <ali.scissons at gmail.com> wrote:

> The plugin isn't complete and not ready for production use, not to mention
> the plugin requires changes with UE4 itself (thus the patches). However,
> not everyone is required to build UE4/plugin from scratch. Once it is
> built, you should be able to redistribute it to your other developers and
> only have them setup with C# related tools like Xamarin Studio and it's
> plugin.
> Ali Scissons
> On Thu, Mar 19, 2015 at 7:34 AM, David Ford <davidfordaus at gmail.com>
> wrote:
>> I'm somewhat confused as to why each developer wishing to use C# "must"
>> recompile from source.  As far as I can see there's nothing compelling
>> within the Mono code that requires that each developer should rebuild for
>> their own specific machine or environment.
>> Can I suggest that the better (best) approach be that a virtualised build
>> environment be established within Xamarin or Unreal / Epic, and that a
>> single developer be tasked with updating the Mono plugin on each release of
>> the game engine (presumably the API's don't change between patches to point
>> releases - eg 4.7 + patch will be compatible with the plugin if 4.7 raw is
>> compatible.  This developer wouldn't be full time, but may perhaps spend a
>> day each month (or less, assuming straightforward compatibility between
>> releases).
>> At this stage there is potentially a vast amount of wasted effort having
>> every C# developer establishing a full Mono build environment and toolchain
>> for C#, when in fact most developers (including myself) simply want to
>> download the Mono plugin and add it to the UDK, then add our own C#
>> assemblies.
>> We currently have one developer spending several days simply getting a
>> Mono C# plugin environment to run, when in reality a pre-built Mono plugin
>> would have removed all of that needless effort, and reduced the time to
>> hours at most.
>> We would prefer to use Unreal rather than Unity, however at this stage I
>> may pull our Unreal development completely and switch our (early phase)
>> project to the Unity platform based solely on the lack of a simplified
>> development toolchain with C# / Mono.
>> Note that all the other code for our project (20 + C## projects, tens of
>> thousands of lines of code) are C#, and I see no reason to add a small
>> amount of C++ purely to support Unreal, and based solely on the fact that
>> recompiling the Mono C# plugin for each UDK release is non-core effort.
>> Best regards
>> David Ford
>> 0421 659 552
>> _______________________________________________
>> Mono-ue mailing list
>> Mono-ue at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/mono-ue

Best regards

David Ford
0421 659 552
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/mono-ue/attachments/20150320/adef374f/attachment.html>

More information about the Mono-ue mailing list