I must admit that my rusty knowledge of .NET hampered my efforts to actually use it, so it took quite a while to even depend on the projekt, so I haven't really done much testing of anything.
But looking at the namespace and method names, my biggest worry is that it's using the Java naming conventions. I'd expect e.g. namespace MetaModel.Core instead of org.apache.metamodel.core and e.g. MetaModelHelper.IsInformationSchema instead of MetaModelHelper.isInformationSchema I'm not sure if the tool you're using will permit that without manually trawling through the code to update references, though. I'll experiment with it tomorrow if time permits. BR, Dennis ________________________________ From: Henry Saputra <[email protected]> Sent: 05 September 2017 20:40:53 To: [email protected] Subject: Re: Port to C# (DotNet Core) 0.2.0 released and answers to feedback Looking at the initiative to port MetaModel to C#, I need to ask what is the motivation to do this. If it is just client bindings to be able to use Apache MetaModel in C#, or other languages for that matter, we could use gRPC and move the interface definition to declarative and allow code gen for different languages. But rewrite the whole project into different language makes bit concern about maintainability and effectiveness in long run. - Henry On Tue, Sep 5, 2017 at 3:38 AM, Dennis Du Krøger < [email protected]> wrote: > I can take a look when I get home from work, but my C#/.NET experience is > ancient, last time I actively used it for anything must have been back in > the 2.0 days... > > Oh well, a good chance to brush up a bit :) > > BR, > Dennis > > -----Original Message----- > From: Kasper Sørensen [mailto:[email protected]] > Sent: 5. september 2017 05:38 > To: [email protected] > Subject: Re: Port to C# (DotNet Core) 0.2.0 released and answers to > feedback > > Hi Michel, > > Thank you for the update on the project :-) I'm definately going to take > it for a spin shortly, but just super busy myself at the moment so I can't > react as quickly as I'd like. > > If anyone else has any C# insights and can poke around a bit, I think that > would be very valuable! > > Kasper > > 2017-08-31 0:36 GMT-07:00 Echopraxium <[email protected]>: > > > Hello Dev team > > > > I've just released v 0.2.0 of a 'port to Csharp' prototype, here it is: > > https://github.com/Echopraxium/apache_metamodel_dotnet_core_bud > > > > Now the codebase is big enough (i.e. the 'engine' is ready) which > > allows to run the unit tests (via 'MetaModel-cli-test' console app) > > but still a lot of validation / debug pending (e.g. in > > JsonDataContextTest.testDocumentsOnEveryLineFile() only the first > > Assert succeeds). Previously I sais that I applied a "brute force" > > and "bottom up" approach. Now I would say that it's more the approach > > seems more like porting a legacy codebase. > > > > I agree with Kasper that a rewrite with CSharp strengths and > > weaknesses makes more sense than a "1 to 1 Force Fit". Beyond that > > each language brings its own set of "design biases" > > with the entropy/negentropy side effect of its idioms. Then my feeling > > is that this prototype may hightlight the parts where such 'bias' > > occured. > > > > I just hope that this prototype may raise enough motivation to start a > > "dotnet" child project within Apache MetaModel. > > > > Best Regards > > > > Michel Kern (echopraxium) > > >
