jongalloway2

.NET is under MIT license (https://github.com/Microsoft/dotnet/blob/master/LICENSE) and there's also a patent promise (https://msdn.microsoft.com/en-us/openspecifications/dn646766). There isn't an "enterprise .NET" version for sale. There are enterprise versions of Visual Studio, servers, etc., but nothing you could feasibly be "accidentally" using, and nothing that you have to use to do .NET dev.

What specific risk(s) are you thinking about?

Disclaimer: Microsoft employee, Nazgûl

Curious what you're looking for in a path+querystring builder.

For ASP.NET controllers, I'd use attribute routing's URL generation: https://docs.microsoft.com/en-us/aspnet/core/mvc/controllers...

If you want a separate library for use outside of ASP.NET, and you want something more sophisticated than UriBuilder, there are several out there. I've used Superscribe in the past, but I just looked around and Flurl looks pretty neat: http://tmenier.github.io/Flurl/

In Visual Studio 2017 RC it's "File / New / xUnit Test Project" and you're all set.

I think some of the docs and presentations have gone a little far to the everything-commandline direction. If you're an experienced .NET dev, you're probably going to be a lot more comfortable with Visual Studio at least to get started. Much easier to start with some working code and break it / play with it than to start at the command line and a project file... again, if you're an experienced .NET dev who's used to Visual Studio.

I will agree with your main point that it is confusing and that it should be easier. Those are actually some of the top things listed on the roadmap.

I'd recommend using the tutorials rather than just typing stuff and seeing what happens. The language and concepts are the same, but there are some big differences at the framework and platform level.

The xUnit tutorial is here: https://www.microsoft.com/net/tutorials/csharp/getting-start...

Those tutorials are pretty intro level, but they do cover some of the issues you ran into.

Also, I'd recommend checking out the new Visual Studio 2017 RC with updated .NET Core tools and support for the csproj based projects: https://blogs.msdn.microsoft.com/dotnet/2016/12/12/updating-...

From how I read this comment, it's not exposed on x86 because it's extremely slow on Atom:

https://github.com/dotnet/coreclr/blob/cb9cbef5cd036bb761720...

The news article is incorrect. Typing cmd from the run dialog still launches cmd.exe.

The release post spells out exactly what's changes - win-x menu, context menu kind of stuff.

I'm pretty sure the Softpedia article is incorrect in saying that "cmd" is now aliased to powershell. I installed the update, and running cmd from search bar (win cmd enter) and from run dialog (win+r cmd enter) both launch cmd.exe.

The release announcement post says "Typing “cmd” (or “powershell”) in File Explorer’s address bar will remain a quick way to launch the command shell at that location."

I honestly kind of wish it was aliases - I regularly launch a cmd window due to decades of muscle memory, then remember I really probably wanted powershell.

It does help that Erich Gamma & team are in Zurich...

There's also a new (preview) python-based CLI that's pretty nice: https://azure.microsoft.com/en-us/blog/announcing-azure-cli-...

There's a lot more technical information in this post (scroll below the video for diagrams and writeup): https://blogs.msdn.microsoft.com/wsl/2016/10/19/windows-and-...

I agree, Visual Studio Gallery is good for Visual Studio related tools.

For NuGet packages, I like http://nugetmusthaves.com/. It uses NuGet download counts, community voting, release date, etc. to give categorized, ranked recommendations.

That address is bit.ly's corporate headquarters: https://bitly.com/pages/contact

I do a lot of presentations, and I'm on the Windows Insiders Fast Ring, meaning I get a new build about weekly, hence a lot more Windows Updates. I check for and install updates as part of my preparations before presenting. I've been doing this for years, on every operating system I present on (yay xcode updates over hotel wifi!). I've never had a problem with unexpected OS updates, because I run them explicitly. I do the same for frameworks and IDEs I'll be demonstrating. I'm surprised someone doing a presentation wouldn't make sure their software was up to date before doing a presentation, honestly. Not just because it makes sure you know the state of your software stack, but because you'll know if - for whatever reason - your demonstrations don't work or work differently on the latest software release.

End to end tech checks (including your software stack) is just part of respecting your audience.

I think some people run into surprise software updates because they do demonstrations on a virtual machine. I don't think that's a good idea, but if you're going to present on VM images, it's just good practice to test out your environment before you present on it.

Note: I'm not making any statement here about how I think software updates should be installed or how Windows works. I've blogged about controlling Windows Updates over the years, here's a post from a decade ago: https://weblogs.asp.net/jongalloway/438009. This comment is about how I make sure, as a developer and presenter, that software updates don't affect my presentations.

Disclaimer: Microsoft employee, Nazgûl

For that example, they're showing Visual Studio opening the Roslyn repo (https://github.com/dotnet/roslyn). Without any package restore, that's 200MB / almost 12k files.

Keeping in mind that Visual Studio isn't a simple text editor, it's a code editor that provides code-based IntelliSense, extensions, integrated debugging, etc., I'd say 30 seconds isn't too bad, especially considering some websites these days take nearly that long to finish rendering.

I'm with you there. For JS/JSX dev, I'm assuming you know about Mads Kristensen's Web Extension Pack (https://visualstudiogallery.msdn.microsoft.com/f3b504c6-0095...) and Node Tools for Visual Studio (https://www.visualstudio.com/vs/node-js/), right?

The roadmap has been built around major releases, with big updates to internals and major new features, a little less than every 2 years for a while (2008, 2010, 2012, 2013, 2015).

But, there have been pretty substantial updates about every 4 months since about 2012 (see https://en.wikipedia.org/wiki/Microsoft_Visual_Studio#2013 and https://www.visualstudio.com/vs/release-notes/). There's a balance between the stability and maintainability big enterprises often want and the feature updates developers (esp. in web and other fast moving segments) want. These updates usually include a lot of new features, pulled in as new VSIX extensions, updates to frameworks, etc., that can add a lot without blocking big corps by significantly changing the core (functionality or user experience). For example, here's the release notes on VS 2013.3: https://support.microsoft.com/en-us/kb/2933779 - there's a ton of stuff, especially when you consider that all the sub-frameworks (e.g. ASP.NET Web API new release) require tooling updates and testing.

As a dev, I want new and shiny ASAP, and VS Code is definitely nice from that point of view. But from the VS point of view, I think the 4 month update cycle has been pretty fast.

Disclaimer: Microsoft employee, Nazgûl

The .NET MVC thing is off.

ASP.NET MVC is a web framework that implements the MVC pattern, as opposed to ASP.NET Web Forms, which was control based. ASP.NET MVC versions 1-5 run on the full .NET framework.

ASP.NET Core includes MVC, and the API has stayed as close asp possible to previous versions of ASP.NET MVC. The lower level bootstrapping / hosting / middleware / config stuff is pretty different (much improved, IMO), but your application code (models, views, controllers, services, etc.) should move from ASP.NET MVC to ASP.NET Core pretty smoothly.

If you want to get ASP.NET set up on Linux, I'd recommend using ASP.NET Core instead of Mono at this point. There's a tutorial on developing ASP.NET Core on OS X with VS Code (https://docs.asp.net/en/latest/tutorials/your-first-mac-aspn...) which will work just fine on multiple flavors of Linux, too.

And VS Code runs on the Monaco editor, which goes back a while before that:

http://www.zdnet.com/article/microsofts-browser-based-dev-to...

http://www.hanselman.com/blog/ARichNewJavaScriptCodeEditorSp...

It does if you hit the keyboard shortcut (alt-space)

Is it a dupe of this one? https://developer.microsoft.com/en-us/microsoft-edge/platfor...

Very cool to see a startup built on .NET and Azure sell for $3B!

Some additional info on tech stack:

https://tech.jet.com/blog/2016/02-05-jet-engine-built-2015/

http://hanselminutes.com/494/jetcom-scales-with-azure-f-and-...

Disclaimer: Microsoft employee, Nazgûl

Yeah, please try again. The problem with a lot of Connect programs is that they were tied to a specific release (MonkeyManager Pro 2008) so bugs that didn't make the cut for the product release just got lost in space (not picked up for MonkeyManager Pro 2010). Part of the reason was that there were always internal bug tracking systems, which was what the dev team was really working from day to day, and these other systems were just inputs to that.

If you look at any of the projects that are on GitHub now, the public issues list is the issues list. You can see all the dev comments, scheduling via labels, pull requests, code reviews, etc.

https://github.com/aspnet/mvc/issues?q=is%3Aissue+is%3Aclose...

https://github.com/dotnet/coreclr/issues?q=is%3Aissue+is%3Ac...

For products that aren't on GitHub, public issue lists like UserVoice have still been a big improvement (in my opinion) because they usually keep the bugs / issues / feedback around until it's fixed, and the votes accumulate so the important issues keep bubbling up.

#wellactually We don't talk about ASP.NET MVC as a separate thing anymore. It's just ASP.NET Core. So you might build an MVC app on ASP.NET Core, or build APIs on ASP.NET Core, etc., but it's all just ASP.NET Core.

The best way to make sure they (we, since I work at Microsoft) get the feedback is by finding out where the product is listening.

A lot of products have UserVoice set up, a lot of dev product teams (dotnet, asp.net, etc.) are looking for GitHub issues.

For Windows 10 I'd recommend using the Windows 10 Feedback Hub - if you hate something about Windows 10, post feedback in the Feedback Hub before you uninstall it.

Visual Studio has this page that explains where best to submit feedback / bugs / feature requests: https://msdn.microsoft.com/en-us/library/b8akas30.aspx

There are lots of us who see your comments on HN / Reddit / Slashdot / etc. but having been part of the Microsoft ecosystem (both inside and out of Microsoft) for many years, I can tell you that there's a huge difference between "I've seen some unhappy comments about X" and "Our feedback numbers show 68% of users want us to improve feature X". Also, specifics are important - a detailed issue report with repro steps and recommendations for what you'd like to see work a whole lot better than "@drunkvs LOL VS suxxxx ikr!!!"

Also, just because I'm an ocd fact checker, Ballmer technically didn't say "open source is a cancer". He said that Linux is a cancer, referring to the strong copyleft license requirements (https://web.archive.org/web/20011211130654/http://www.suntim...). [yes, I very well know that you can run software on Linux without that software being GPL. I'm writing this from Red Hat DevNation :)]

Regardless, I can tell you that our current CEO and everyone I work with is excited about writing great software that runs everywhere.

Fixed: https://github.com/Microsoft/monaco-editor/pull/12

Yep. Last month I was in Moscow for a conference keynote and a workshop. Running through demos the morning before, I spilled coffee on my Lenovo and fried some keys on the keyboard. Thought a bit, pulled out my MacBook Air, and had everything running in time for a keynote rehearsal that evening. Nice stress test of the cross-platform mindset, not quite as nice of a stress test for me though.

I do that sometimes, but that's kind of weird too. If you're reading a tutorial that keeps flipping between browsers, it calls attention to the browser rather than what you're learning about. We do sometimes flip between browsers for conference demos - I try not to call attention to it - just use a few different browsers and people who notice that kind of thing will see it.

As a Microsoft employee who works on conference presentations, works on hands on labs, etc., you can't win on this.

If I use Edge exclusively in screenshots, people assume it's not cross-browser, it's not cross-platform, Microsoft is out of touch with other developers, Microsoft's living in a bubble, etc.

If I use other browsers for screenshots, I get comments like this.

As @dangrossman replied, we all use whatever browser we want for day to day browsing.

As a professional web dev, I make a habit of cycling through the modern browsers because it's just a good practice. I was the annoying guy in my dev team (not Microsoft, a financial services company) in the early 2000's that tested everything in Firefox when everyone else just wanted to use IE6 all the time. I'm typing this in Edge now, last week was a Chrome week.

[please don't downvote the parent comment]

Here's a very recent technique that renders an input string based on analysis of handwriting samples: http://visual.cs.ucl.ac.uk/pubs/handwriting/