[MonoDevelop] Customizing XIB code generation

Len Charest len at shingl.com
Wed Oct 17 15:58:45 UTC 2012


> What exactly do you want to do?

I want to prevent generation of the ReleaseDesignerOutlets method on each
of my controller classes. This would be an optimization; nothing in the
existing generated code is preventing my app from functioning properly.

Nevertheless, it's odd that a codegen template exists but is not used (save
for the initial, outlet-free designer content). It would be cool if codegen
were fully customizable via a T4 template.

On Sat, Oct 13, 2012 at 2:04 PM, Jeff Stedfast <jeff at xamarin.com> wrote:

> Hi Len,
>
> I don't think you can customize it at all, it's internal to MonoDevelop.
>
> What exactly do you want to do?
>
> Jeff
>
> On Tue, Oct 9, 2012 at 12:58 PM, Len Charest <len at shingl.com> wrote:
>
>> I'm using MonoDevelop 3 with Monotouch to write an iPhone app. I'd
>> like to customize the designer files (*.designer.cs) generated by MD
>> for each of my XIB files. Specifically, I'd like to eliminate the
>> ReleaseDesignerOutlets method generated for each controller class.
>>
>> I've found the template used to create new iPhone view controllers (in
>>
>> /Applications/MonoDevelop.app/Contents/MacOS/lib/monodevelop/AddIns/MonoDevelop.IPhone/templates-files/IPhoneViewController.xft.xml).
>> The template is used to create the initial content of a designer file,
>> but it seems to be ignored when the designer file is re-generated
>> after an edit to the corresponding XIB. In other words, my changes to
>> IPhoneViewController.xft.xml are not sufficient to get the result I
>> want.
>>
>> Suggestions?
>>
>> Thanks,
>> Len
>> _______________________________________________
>> Monodevelop-list mailing list
>> Monodevelop-list at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/monodevelop-list
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/monodevelop-list/attachments/20121017/e55d93a5/attachment.html>


More information about the Monodevelop-list mailing list