Closed kipusoep closed 8 years ago
Mmm... weird: we do have some code that manages "ambiguous symbols" and is supposed to prepend global::
to types that would otherwise be ambiguous. Can you give me the entire list of 'using' clauses that come at top of the generated file?
using System;
using System.Collections.Generic;
using System.Linq.Expressions;
using System.Web;
using Umbraco.Core.Models;
using Umbraco.Core.Models.PublishedContent;
using Umbraco.Web;
using Umbraco.ModelsBuilder;
using Umbraco.ModelsBuilder.Umbraco;
Wondering why the compiler would think Umbraco.Something is Infocaster.Umbraco.Something if there is no using clause for Infocaster - how would the compiler know about it? (or am I missing something obvious)?
I think because I'm inside the namespace 'InfoCaster.Something' ;-)
Aha - probably overlooked that one. So your models' namespace would be eg Infocaster.Models
, right? OK, looking into it.
Exactly :-) Great!
Reproduced, fixed in 3.0.1.
Thanks, nice work! :+1:
First of all; thanks for creating this nice tool, it's great :-)
I ran into an issue with the default umbracoFile property inside the generated Image class:
We have used the namespace '
Infocaster.Umbraco
' a lot and so the compiler thinksUmbraco.Something
meansInfocaster.Umbraco.Something
. To fix this we needglobal::Umbraco.Something
. Could you add this to the generated models?