Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Visual Studio 2017 Release Candidate

visualstudio.com

Post reply on HN
Print view View original

81–90 of 121 posts

Re: Visual Studio 2017 Release Candidate

#81

Post by Maarten88 »

billforsternz wrote: post #61
cptskippy wrote: post #59

Earlier quoted context omitted.

There's some sick bastard in Microsoft who really likes these confusing sames. He's probably the same guy who came up with .NET. Remember when .NET could refer to virtually every product Microsoft made? I was half expecting them to call it Visual Studio Surface. Then you could run Surface on your Surface on any Surface on the planet.

Indeed, .NET must be the worst, most misleading, least googleable product name ever. I suppose we should be grateful that MS called an earliest technology COM not .COM.

I must say Google handles it well. I'm searching with these terms quite often and Google knows .NET == dotnet ~ C# and finds results without much problems.

Re: Visual Studio 2017 Release Candidate

#82

Post by moogly »

hudo wrote: post #22

Project.json for .net core is gone, there's xproj file. How to change settings, like target framework, per-framework dependencies, build options, pre/post build steps, etc? I don't see any tooling support for that.

Nitty gritty details and examples here https://blogs.msdn.microsoft.com/dotnet/2016/11/16/announcin...

Re: Visual Studio 2017 Release Candidate

#83

Post by Tactic »

b_lindahl wrote: post #38

Visual Studio "15" = Visual Studio 2017 = VC 15.0 Crystal clear. Why didn't Microsoft bump up VC version to 17 to sort of make VC version follow VS version. Would clear out some confusion going forward.

This is what happens when marketing determines your version names.

Re: Visual Studio 2017 Release Candidate

#84

Post by robotdad »

sremani wrote: post #18
Maarten88 wrote: post #9

One of the install options is "Linux development with C++"

That is the natural extension of Linux Subsystem on Windows.

PM for this at MS. We do work with WSL but do not rely on it. Currently we treat it as another remote Linux machine, just setup SSH in WSL and we'll work

Re: Visual Studio 2017 Release Candidate

#85

Post by robotdad »

TheCoreh wrote: post #37
LyalinDotCom wrote: post #14

Earlier quoted context omitted.

Yes our C++ team has been investing into this area for a while now, we're building some really powerful debugging capabilities there as just one thing to mention with remote debug right out to your Linux machine or VM

Does that mean VS will support C11 features?

The Linux workload is designed to work with GCC today, so whatever standard level your GCC compiler supports is good.

Re: Visual Studio 2017 Release Candidate

#86

Post by jimmaswell »

FLGMwt wrote: post #13

As a .NET dev, I'm happy to see this: "a new way of view, edit, and debug any code without projects and solutions" Seems silly, but this solves a long time gripe w/ VS.

Good for small scripts in python etc I guess? Otherwise, when would you want the IDE's abilities but constrained to one file?

Re: Visual Studio 2017 Release Candidate

#87

Post by kodfodrasz »

cptskippy wrote: post #59
douche wrote: post #43

Earlier quoted context omitted.

The naming has been awful with this release in particular. Having two Visual Studio (20)15s out at the same time is very confusing. Almost as bad as the Skype vs Skype for Business marketing boondoggle.

There's some sick bastard in Microsoft who really likes these confusing sames. He's probably the same guy who came up with .NET. Remember when .NET could refer to virtually every product Microsoft made? I was half expecting them to call it Visual Studio Surface. Then you could run Surface on your Surface on any Surface on the planet.

On the other hand if you want an SQL server how does MS call it? SQL Server. Unlike for AWS you don't need a glossary to get around in Azure. (At least less so) This is why this disparity in naming thing very simply and straightforward and mind-boggingly badly is incomprehensible for me.

Re: Visual Studio 2017 Release Candidate

#88

Post by samb1729 »

jimmaswell wrote: post #86
FLGMwt wrote: post #13

As a .NET dev, I'm happy to see this: "a new way of view, edit, and debug any code without projects and solutions" Seems silly, but this solves a long time gripe w/ VS.

Good for small scripts in python etc I guess? Otherwise, when would you want the IDE's abilities but constrained to one file?

You aren't necessarily limited to editing single files without project files. Lots of projects are folder-based with tasks or commands to be run on that folder structure.

See: Rails apps, Hugo websites, anything written in Go.

Re: Visual Studio 2017 Release Candidate

#89

Post by kodfodrasz »

timsneath wrote: post #68
Zitrax wrote: post #60

Earlier quoted context omitted.

That sounds awesome. Is there an offline installer yet ?

Yes - the release notes describes our initial capabilities on that front: https://www.visualstudio.com/en-us/news/releasenotes/vs2017-... Essentially, you can run /layout on the installer to create an offline installation cache. We're working to add more capabilities here, but the fundamentals of the experience are in place.

Do you plan to package it to a sandboxed windows store app? Would it loose too much functionality that way? The garbage uninstalls left behind by earlier (and current) versions makes me think this might be a solution.

Having it installable via the store would be not only convenient, but also a good promo for devs to package their other legacy apps.

Re: Visual Studio 2017 Release Candidate

#90

Post by m-zuber »

omerraviv wrote: post #51
m-zuber wrote: post #48

Earlier quoted context omitted.

It might be, but Alive was much more than just if the tests pass or not

Might be. Also, in any case - this adds stuff that wasn't in the original Alive AFAIK - supposedly it knows to only run tests that were affected by your last edit and show line-by-line red/green/gray coverage indicators: did someone say NCrunch?

Correct. Alive was focused on a chosen method - so you chose one method, the test case to check that method, and then it ran. You could then check what execution would look like in called methods, but it was not project/solution wide.
Post reply on HN