Live data from Hacker News

ASP.NET MVC, Web API, Razor and Open Source

weblogs.asp.net

41–50 of 104 posts

Re: ASP.NET MVC, Web API, Razor and Open Source

#41

Earlier quoted context omitted.

ReSharper can download source code over the internet or do I have to setup things manually? put them in the right place, etc?

Its automatic. If it can't get the source, it will use its built in decompiler, and produce surprisingly readable source anyway (I force it to this mode by default, due to a flaky internet connection).

How does ReSharper managed to locate the 3rd-party source code?

Does ReSharper have their own source repository or some sort?

Re: ASP.NET MVC, Web API, Razor and Open Source

#42

Earlier quoted context omitted.

Its automatic. If it can't get the source, it will use its built in decompiler, and produce surprisingly readable source anyway (I force it to this mode by default, due to a flaky internet connection).

How does ReSharper managed to locate the 3rd-party source code? Does ReSharper have their own source repository or some sort?

As the parent listed, Resharper by default will download MS sources for BCL. For a third party, it will show the decompiled source.

Re: ASP.NET MVC, Web API, Razor and Open Source

#43
post #17
post #14

Also worthy to note that Microsoft's BizSpark program provides free production access to Microsoft tools and products-- not Express editions but versions like Visual Studio Ultimate, SQL Server Enterprise, Windows Server Enterprise, etc. You also get a couple thousand free hours on Azure if you want to go that route. For training you also get three months of Pluralsight which brings you up to speed on the relevant to…

Wait until the bill comes.

The most expensive part of a software project is the people, not the licenses. People who pay for MS believe that they're saving money in the long run.

Re: ASP.NET MVC, Web API, Razor and Open Source

#44
post #17

Earlier quoted context omitted.

Wait until the bill comes.

The most expensive part of a software project is the people, not the licenses. People who pay for MS believe that they're saving money in the long run.

The increased engineering burden of having to consider software license costs when designing systems hardly seems worth it. Imagine if you had to pay a per-node fee for your Hadoop cluster? How much extra effort would be put into optimizing the individual performance of each node and job if there were an additional 50% per-node cost to run it?

Re: ASP.NET MVC, Web API, Razor and Open Source

#45

Earlier quoted context omitted.

After three years, you get to keep some production licenses as well as all the software you downloaded for free. You get four Windows Servers and two SQL Servers. This really is a great program. You can read more here: https://www.microsoft.com/bizspark/About/Graduation.aspx

Yeah, there's a common misconception that there's a big bill coming at the end. There isn't - you get to keep the software you used during the 3 years for no charge and you get discounts if you need to buy more.

Uh, there is a big bill coming at the end. You need to keep your system running, even though you now have to pay for licenses, don't you?

When building your system during BizSpark, you are unlikely to make architectural choices with respect to software licenses, because they are free. Then you graduate, and you're probably looking at a system that uses way more licenses than it would have if you had to optimize around that parameter from the get go.

BizSpark is an excellent move by Microsoft, and likely is helpful for folks starting out who already know the .NET stack. But I'm very skeptical that working in the Microsoft stack offers such a technical advantage that it is worth the risk that your business is not going to be in a position to suddenly have its operational costs bloated by software licenses by some arbitrary date determined by Microsoft.

Re: ASP.NET MVC, Web API, Razor and Open Source

#46
post #11

I would consider paying for .net if it received first class treatment on Linux. As someone who has lived through the pain of hosting apps on Windows, I just refuse to do it in the future. I'd love to see Microsoft bring Mono into the fold and truly bring it to the level of the Windows .net implementation.

I used the .net stack for 8 years. But, I wouldn't use the platform for a startup or my own projects. I don't want to be locked into the Windows platform. Mainly, because of licensing fees and just a general preference for the Linux shell and its scripting environment.

The open source community isn't very strong so there aren't as many options for a lot of things, and the community has relied on Microsoft to provide most of the tools and libraries.

Also, while C# is a nice language, I don't find it that different that it compels me to use it over other options available elsewhere. Personally, I find F# to be a much more compelling product.

Re: ASP.NET MVC, Web API, Razor and Open Source

#47
post #45

Earlier quoted context omitted.

Yeah, there's a common misconception that there's a big bill coming at the end. There isn't - you get to keep the software you used during the 3 years for no charge and you get discounts if you need to buy more.

Uh, there is a big bill coming at the end. You need to keep your system running, even though you now have to pay for licenses, don't you? When building your system during BizSpark, you are unlikely to make architectural choices with respect to software licenses, because they are free. Then you graduate, and you're probably looking at a system that uses way more licenses than it would have if you had to optimize aroun…

Yes and no. The point is that you're not retroactively billed for licenses you got while in the program. Believe it or not, a lot of people seem to think that it's just a delayed payment program. Yes, if you're designing a system that's going to require more than 6 servers you might end up paying for a license. Windows Web Server runs ~$470. But for many businesses, if you're using >6 servers you're likely going to be deploying to some cloud hosting solution, or possibly using a shared hosting service (which would include licenses).

It's a tired example, but StackOverflow really is an example of a startup that got a lot done with very few devs or servers and launched a very successful business. Also key is that you can mix and match technologies as you want, something that the StackOverflow used very intelligently (e.g. Microsoft server fronted by non-Microsoft reverse proxy, etc.).

Re: ASP.NET MVC, Web API, Razor and Open Source

#48
post #35

Earlier quoted context omitted.

That is strange. I'm the other way around: it is painful for me and my team to switch Java/Eclipse/Maven to C#/VS.NET/NuGET since NuGET isn't even close to Maven. Not to mention we have to deal with licensing, buying software tools, etc while in Java land almost all the high quality tools are free, easy to download, easy to install. Setting up a new machine is a breeze with SVN/GIT + Maven. A breeze.

NuGet vs Maven seems like a small issue when compared to VS vs Eclipse or even C# vs Java. In the latter two, MS wins hands down. I can cope with NuGet.

Don't want to get into a silly argument, but while you are right that VS beats eclipse, IntelliJ IDEa absolutely spanks VS. IMO jetbrains is hands down the best dev tools company around nowadays

Re: ASP.NET MVC, Web API, Razor and Open Source

#49
> I am a developer who has leaned towards .NET over the last few projects and one of the things that used to nag me is that the platform is a closed one (and the licensing fees can be a decent part of the cost). I was fairly certain I would migrate off it if the project ever took off seriously.

Can you explain why? Is it because the only reason it's closed? You just hate MS.

Re: ASP.NET MVC, Web API, Razor and Open Source

#50
post #6

I am a developer who has leaned towards .NET over the last few projects and one of the things that used to nag me is that the platform is a closed one (and the licensing fees can be a decent part of the cost). I was fairly certain I would migrate off it if the project ever took off seriously. And after seeing the C# love on HN on the poll for favorite programming languages last week, I realized there must be many ena…

For a big old school company like Microsoft to accept patches from the community is huge. I always grudgingly accepted there must be some sort of commercial risk ("Microsoft used my code and made 10 million dollars, now I'm going to sue them") holding them back.

Does anybody have insight on this topic? I'm currently building something that would benefit greatly from user contributions of code, but I'm wary about the legal implications (the project will be a commercial site, and while I have no problem publishing their code if I choose to integrate it into my site to enhance the user experience, I have no interest in publishing the core code for the rest of the site).

Post reply on HN