Source code of ASP.NET
21–30 of 104 posts
Re: Source code of ASP.NET
#22Not all of ASP.NET though...notably absent: Web Forms.
Re: Source code of ASP.NET
#23Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.
Too little? Biggest change for ASP.NET from release of ASP.NET! "Too much of pain" was the first (and last) thing I said when trying to configure ruby on ubuntu. Or tried to download some app and run it.
Re: Source code of ASP.NET
#24Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.
I don't understand the thinking behind phrases like "too little, too late" about a company whose tooling will likely span the entire careers of a number of generations of developers.
Re: Source code of ASP.NET
#25Re: Source code of ASP.NET
#26Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.
Visual Studio a) will never run on Unix, and b) is not required to do .NET development. I know people who do their .NET work in Sublime Text with a nant build chain. It's not my preferred method, but it works great for them. Hell, I know a guy that uses ASP.NET to host an Angular app, and to unify his build system, he has Grunt pick up the heavy lifting of running his MSBuild files whenever he does the pre-deploy ste…
Re: Source code of ASP.NET
#27Re: Source code of ASP.NET
#28Re: Source code of ASP.NET
#29Is this admission that codeplex is dead?
I don't think there is a mandate for all MS project to be on codeplex which is somewhat surprising.
Re: Source code of ASP.NET
#30Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.
I don't understand the thinking behind phrases like "too little, too late" about a company whose tooling will likely span the entire careers of a number of generations of developers.