Is there something like Heroku but for dotnet core apps?
I'd like to play a bit with it but it should be as easy as pushing to a repo to deploy and run.
Performance Improvements in .NET Core
71–80 of 94 posts
Re: Performance Improvements in .NET Core
#72Is there something like Heroku but for dotnet core apps? I'd like to play a bit with it but it should be as easy as pushing to a repo to deploy and run.
Why do you need to push to a repo to deploy/run? If you want to play just create a project and run it locally.
Re: Performance Improvements in .NET Core
#73Is there something like Heroku but for dotnet core apps? I'd like to play a bit with it but it should be as easy as pushing to a repo to deploy and run.
You can easily deploy them to GCP's AppEngine Flexible with a simple dockerfile. It's pretty close to the 'git push heroku master' experience.
https://cloudplatform.googleblog.com/2016/10/how-to-use-Dock...
Re: Performance Improvements in .NET Core
#74Earlier quoted context omitted.
https://www.microsoft.com/net/core#linuxredhat I see. 4 steps too hard. I bet you're a Go code monkey?
Actually the instructions for Debian are the best: download the tarball, adjust $PATH and go: https://www.microsoft.com/net/core#linuxdebian But I went "ubuntu" route and bailed, looking for a simple tarball.
Why is the Ubuntu route too difficult?
Re: Performance Improvements in .NET Core
#75Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
Yo! Great point! In fact current dotnet core site was hugely inspired by golang one (IMO). Just take a look: http://dot.net/ There's also a great 20 lesson in-browser interactive tutorial (there's also F# and VB version!): https://www.microsoft.com/net/tutorials/csharp/getting-start... I'd also like to stay on this cool dot.net domain though, microsoft.com might scare people.
And there's other open source project like mine github.com/dodyg/practical-aspnetcore
Re: Performance Improvements in .NET Core
#76Earlier quoted context omitted.
> I still haven't quite grasped the relation between core and the full framework when it comes to fixes like this being merged into the full framework. From what I can tell, from following the CoreCLR repo ( https://github.com/dotnet/coreclr ), it's changed over time. In the beginning the sources of the 2 were more closely tied, changes were (automatically?) copied over. Now it seems like it's more ad-hoc, done as an…
If you take a look as these issues, it's clear that they're happy to make the source code very different, i.e. hard/impossible for changes to be automatically ported across. Just look at how much .NET Framework (Desktop) code they removed from CoreCLR earlier this year! - https://github.com/dotnet/coreclr/issues/8857 - https://github.com/dotnet/coreclr/issues/8763 - https://github.com/dotnet/coreclr/issues/4651 - htt…
FWIW (I work on the .NET Team and I wrote the mirror we use to keep TFS and GitHub in sync). When we started the project we maintained a mirror which kept our GitHub repository and internal TFS branch in sync. After a while, we decided that trying to maintain this was more harm that it was worth (the internal TFS branch used a completely different build system and there were other interactions between code which had been open source and code that hadn't that meant our internal branch was on the floor every few days), in addition it meant that we were carrying around a bunch of effectively dead code in the source tree.
We still do mirror some code (mainly the JIT) into TFS to make it easier to share code with the Desktop in an automated fashion. However, for the rest of the code (e.g. the VM and BCL), if there are improvements we want to bring back, an engineer will just port them manually.
Re: Performance Improvements in .NET Core
#77Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
My experience has largely been the same, the whole mono, xamarin, vs studio, etc of tooling (whatever it all is) is a tragedy of good technology made useless. The licensing, tooling, and runtimes are such a mess I give up before I begin. There needs to be one canonical way to do things on every platform, this "band-aid" approach might've worked when you first open sourced but surely no longer does the job. I'd love t…
>this "band-aid" approach
I've been putting food on the table as a .net specialist for fifteen years. My impression is that .Net 4 is a band-aid of Windows-dependent implementations and that .Net Core is some solid tech, using industry's best practises for streams, collections, GC and so on. How do you think they made it portable?
I started to get pissed off at MS at around the time MVC 3 came out. That was not the direction I would have taken. Oh the bloat. Asp.Net Core Mvc is a dream. You start out with nothing, basically. Invent your own conventions.
I'm happy to not touch .Net 4 again. Love Core.
Edit: as parent said though: Microsoft, your tooling has gone from best-of-breed to just-another-messed-up-ide. Please remove everything you copied from Resharper from Visual Studio. It just doesn't work. Try renaming a file. I have never had anything but near-fatal studio errors such as "the refactoring of the file name just didn't work, man, crashing soon...". I want my Resharper back. Can you disable your stuff? I mean, all of it? And please don't ask me to develop server applications on a javascript client such as VS Code. Nut gunna do it.
Re: Performance Improvements in .NET Core
#78Every time I try to get a quick feel of .NET on Linux, I allocate an hour to it and that hour is always spent wandering around various guides on microsoft.com and never getting anything done. There are terms like .NET Core, .NET Platform, .NET Framework, .NET SDK all mixed up on nearly every page, multiple versions of "Getting started" and "Quick start" guides, massive navigation menus and options on every page so yo…
I have followed: https://www.hanselman.com/blog/PublishingAnASPNETCoreWebsite...
Worked like charm had site up and running in 20 mins which is kind of "production" ready. With supervisor and reverse proxy. Or just do docker? You are overthinking a bit also with the terms, you don't need to know those terms by heart.
Re: Performance Improvements in .NET Core
#79Is there something like Heroku but for dotnet core apps? I'd like to play a bit with it but it should be as easy as pushing to a repo to deploy and run.
I would say Azure. Push deploy is very easy to setup.
Re: Performance Improvements in .NET Core
#80Earlier quoted context omitted.
My experience has largely been the same, the whole mono, xamarin, vs studio, etc of tooling (whatever it all is) is a tragedy of good technology made useless. The licensing, tooling, and runtimes are such a mess I give up before I begin. There needs to be one canonical way to do things on every platform, this "band-aid" approach might've worked when you first open sourced but surely no longer does the job. I'd love t…
Definitely seconded. Do a bit of .NET (non-core) maintenance too, so it's not like I'm completely unfamiliar with it. Though, maybe legacy knowledge isn't helping...
Having knowledge about legacy (Microsoft) tech is not bad if you're good. Many companies I know run their business on VB.Net/WebForms/Knockout/ELK/MSSQL. We do at my current gig. You have to be its mother to love that stack.