51–60 of 68 posts
> If not what are the reasons for a startup to stay away from .NET CORE? .NET's text-to-speech isn't available in .NET Core, much less on Linux.
Isn't that because .NET's TTS is just a wrapper around OS-provided TTS services?
My startup is based on Windows, the .NET Framework, ASP.NET for Web pages, and ADO.NET for interacting with SQL Server. For the programming language, I'm using Visual Basic .NET -- as Kernighan and Ritchie, IIRC, stated in their C , the lanugage has an idiosyncratic syntax, which it turns ou I don't like. Since C# borrows some of that syntax, I prefer the more traditional (like PL/I, Pascal, Fortran, Algol, etc.) syn…
I'm the lead developer on a startup and all of our backend code is .net core (the frontend is still 4.5)! I love it. Feel free to PM for more info.
Do you use EF at all? I'm interested in DNX but only EFC works on DNX, not EF6, and EFC is missing so much necessary functionality (Lazy-loading, Linq joins, Complex types, etc) it's a total no-go for the projects I do that all tie-in with databases.
Earlier quoted context omitted.
Do you use EF at all? I'm interested in DNX but only EFC works on DNX, not EF6, and EFC is missing so much necessary functionality (Lazy-loading, Linq joins, Complex types, etc) it's a total no-go for the projects I do that all tie-in with databases.
Have you looked into nHibernate's support for .net core? It was always more flexible than EF anyway, I've been watching EF slowly fix their design mistakes to be more like nHibernate since version 1.
I am guilty of not staying on top of trends outside the MS camp. I does NHibernate now offer parity with EF? I just don't want to write SQL/HQL in strings.
Earlier quoted context omitted.
Have you looked into nHibernate's support for .net core? It was always more flexible than EF anyway, I've been watching EF slowly fix their design mistakes to be more like nHibernate since version 1.
I haven't. I've been "loyal" to EF since the LinqToSql days, though I did use NHibernate heavily about 10 years ago. My main draw is the quality of the tooling and the nice EDMX model designer. The other draw is Linq support for compile-time type-safe queries (which I've noticed are compiled into good SQL with less mangling than I'd expect). I am guilty of not staying on top of trends outside the MS camp. I does NHib…
Earlier quoted context omitted.
The question was about .NET Core, and I wrote about .NET which likely is closely related. It is likely that my use of .NET is also use of some of what is in .NET Core. So, I answered based on what I know about .NET which should be relevant to the question. Others can be more clear on what is the same, similar, or different between .NET and .NET Core. Then the parts of .NET Core that are also in .NET can get something…
.NET core is a complete rewrite with incompatible API, it has little to do with the old .NET legacy framework. That's MSFT, one days hip API is tomorrows legacy cruft, you better stay on the edge or choose a stable non-MSFT open source solution.
Sounds like .NET Core is aimed mostly just at the Linux world or the mobile world or people who want to be able to run the same code on both Linux and Windows. But I'm staying with Windows desktop and Windows Server -- already spent too much on getting good enough with Windows.
I have to suspect that Microsoft will continue to support Windows developers, including with VB.NET. If all Microsoft does with VB.NET is fix bugs, then fine with me. I'm not sure I have yet found a bug; so, fixing bugs in VB.NET should be easy enough for Microsoft.
I'm not really a programmer; instead I'm an applied mathematician and business man who also writes software. Since this thread is about startups, the core of my startup is some applied math I derived -- and then programmed, with a Web site for the users.
I would guess that if Microsoft wants all their major languages to run on both Windows and Linux, then that will be a lot of work and something for the future that I don't have to worry about.
While I don't like the C# C-like syntax, I could use C# if I needed to. IIRC there is a source code translator from VB --> C# and, maybe, if possible, in the other direction. So, I could convert my code to C#.
I suspect that I'm not the only developer who wants to continue with VB.NET and the .NET Framework as they have been for some years now. If the .NET Core is not relevant to such developers, then so be it, and that's not a good reason for Microsoft to abandon their old developers.
Earlier quoted context omitted.
I agree 100%. My last place was a 100% MS shop and while .NET core seems like it will be great we ran into endless problems, specifically with compatibility and existing libraries. We couldn't get anything more than a toy project to work. I recommend anyone looking at .NET core to use Java for now. The languages are basically mutually intelligible and while java is a bit less syntactically pleasant it gets the job do…
>I agree 100%. My last place was a 100% MS shop and while .NET core seems like it will be great we ran into endless problems, specifically with compatibility and existing libraries. We couldn't get anything more than a toy project to work. This has been my experience with MS in general. Initially everything seems great and you feel productive, but as soon as you decide to go off-road you lose all that you gained and…
Earlier quoted context omitted.
I agree 100%. My last place was a 100% MS shop and while .NET core seems like it will be great we ran into endless problems, specifically with compatibility and existing libraries. We couldn't get anything more than a toy project to work. I recommend anyone looking at .NET core to use Java for now. The languages are basically mutually intelligible and while java is a bit less syntactically pleasant it gets the job do…
>I agree 100%. My last place was a 100% MS shop and while .NET core seems like it will be great we ran into endless problems, specifically with compatibility and existing libraries. We couldn't get anything more than a toy project to work. This has been my experience with MS in general. Initially everything seems great and you feel productive, but as soon as you decide to go off-road you lose all that you gained and…
We're currently evaluating ASP.NET Core for a task manager with web UI for our .NET application (a data transformation tool). Our target audience is people with little or no technical background therefore we can't ask them to setup IIS. I looked at other web-servers in .NET stack (e.g. Suave), but nothing looked sufficiently lightweight and easy to use. Although, we're looking for ASP.NET Core over .NET 4.5.1, not .N…