4 ms·

I've spent at least the last 10 years (including Uni days) writing mostly Java or .NET in some form or other. I don't mind Java, I generally like using Java 8,

I've spent at least the last 10 years (including Uni days) writing mostly Java or .NET in some form or other. I don't mind Java, I generally like using Java 8, but I would happily be writing C# instead if I could run it as easy in as many places. The syntactic sugar, Linq, the latest MVC framework, etc- are generally much faster to get moving in and don't require the configuration hell you can run into w/ Java. However, as a guy who ALSO maintains the servers and deployment process for the things we build, I'll continue avoiding .NET until it can be built, archived, and deployed as easily as we do our Java based applications. I don't think I could even maintain a Windows Server now if I had to.

UK-AL 10y ago
What's hard about building and deploying .net applications? Currently use octopus, which probably one of the best deployment experiences. .Net core runs on linux, so you don't even need a windows server.
cableshaft 10y ago
We use Octopus Deploy at work to deploy .NET. There's a bit of a learning curve, and it has a few quirks and annoyances, and you might need to write some Powershell scripts to fill in a few gaps (which it can run), but once you've got it in place, it's super simple to deploy everything. Every single deploy used to be a big hullabaloo at our company, now it's super smooth thanks to Octopus. If you're talking about Ant, Maven, Tomcat, etc for Java deployment, it's been about 5 years since I've had to use that, but I'd say Octopus is a much better process than that.
- manyxcxi 10y ago
  We tried using Octopus (3 years ago) as part of our CI/CD pipeline and ran into a big problem with it choking on file sizes and handling all the bundled dependencies we threw at it. Eventually we just scripted MSBuild and archived them ourselves for retrieval when we needed them.
  - cableshaft 10y ago
    We don't have anything too huge we give it. I think our largest package is like 100MB. But we do have about 40 active projects in its system. Also, I attended something by a guy who worked for Accenture, who talked about using it with thousands of active projects and some of the technical issues they had to overcome (and work directly with Octopus team to help resolve, at some points) with such a massive amount of projects. It was this guy that gave the talk, he has a blog with lots of information about his experience with Octopus. A few of the quirks I encountered when getting everything set up with our company were resolved by reading his blog: http://ianpaullin.com/category/octopus-deploy/ http://ianpaullin.com/category/octopus-deploy/
holydude 10y ago
I am a unix a guys that recently moved to a MS wonderland. I have to tell you Windows Server and the tooling feels much more polished than Linux and the mess around it. And powershell...powershell is kind here.

UK-AL 10y ago

What's hard about building and deploying .net applications? Currently use octopus, which probably one of the best deployment experiences. .Net core runs on linux, so you don't even need a windows server.

cableshaft 10y ago

We use Octopus Deploy at work to deploy .NET. There's a bit of a learning curve, and it has a few quirks and annoyances, and you might need to write some Powershell scripts to fill in a few gaps (which it can run), but once you've got it in place, it's super simple to deploy everything. Every single deploy used to be a big hullabaloo at our company, now it's super smooth thanks to Octopus. If you're talking about Ant, Maven, Tomcat, etc for Java deployment, it's been about 5 years since I've had to use that, but I'd say Octopus is a much better process than that.

manyxcxi 10y ago
We tried using Octopus (3 years ago) as part of our CI/CD pipeline and ran into a big problem with it choking on file sizes and handling all the bundled dependencies we threw at it. Eventually we just scripted MSBuild and archived them ourselves for retrieval when we needed them.
- cableshaft 10y ago
  We don't have anything too huge we give it. I think our largest package is like 100MB. But we do have about 40 active projects in its system. Also, I attended something by a guy who worked for Accenture, who talked about using it with thousands of active projects and some of the technical issues they had to overcome (and work directly with Octopus team to help resolve, at some points) with such a massive amount of projects. It was this guy that gave the talk, he has a blog with lots of information about his experience with Octopus. A few of the quirks I encountered when getting everything set up with our company were resolved by reading his blog: http://ianpaullin.com/category/octopus-deploy/ http://ianpaullin.com/category/octopus-deploy/

holydude 10y ago

I am a unix a guys that recently moved to a MS wonderland. I have to tell you Windows Server and the tooling feels much more polished than Linux and the mess around it. And powershell...powershell is kind here.