Live data from Hacker News

Visual Studio 2017 Launch [video]

launch.visualstudio.com

101–110 of 177 posts

Re: Visual Studio 2017 Launch [video]

#101
post #95
post #79

Earlier quoted context omitted.

>more than 5 developers *more than 5 developers using visual studio community

Good point, thanks. Still close to useless for professional use, which I guess is Microsofts idea.

Good enough if your company has a small but experienced IT department with a few designers, a bunch of front-end guys on SublimeText and a handful of .NET guys.

Re: Visual Studio 2017 Launch [video]

#102
post #88

Earlier quoted context omitted.

C++ would not have helped as a target language for compiling Ragel, at the level the compiling is done. Actually IIRC Ragel enhanced their output to mitigate that kind of situation, and the intermediate language they target is still C. I'm not sure anybody targets C++ as an intermediate language when emitting code at this level. (I do have written some code that emits some C++, but at a wildly different and higher le…

Of course it would have helped if they made use of a std::vector like class with bounds checking enabled, instead of a pure C array. "Many years later we asked our customers whether they wished us to provide an option to switch off these checks in the interests of efficiency on production runs. Unanimously, they urged us not to--they already knew how frequently subscript errors occur on production runs where failure…

I'm still unsure of the rate at which this could be a solution to leverage checked C++ library types, and whether in the precise case of the Cloudfare issue this would be applicable. However I still think that in most case if you must handle out-of-bound conditions from a checked language outputting to an unchecked one, you just emit your checking code yourself...

Also the C++ standard is 1500 pages long. I prefer to avoid knowing that as a backend language when I can...

Re: Visual Studio 2017 Launch [video]

#103
Is it viable for those of us with only a handful of GB free in our C: drives? 2015 and previous would only put a few bits in the "install location", and still pollute the C: drive with up to 20 GB of stuff of hardcoded paths.

Re: Visual Studio 2017 Launch [video]

#105
post #53
post #3

I really hope they add wildcard (e. g. src/*.cpp) support in C++ project files

Visual studio already supports this in 2015 and older iirc, at least for C# and SQL projects, but it's an undocumented feature. You have to close and re-open the project if you add/remove a file so it notices that it's different. part of the new project system that grew out of the ill-fated project.json is to make this a first-class experience, but again that's focusing on the .csproj, I have no idea if it applies to…

It also works in C++ projects. But it breaks a bunch of IDE stuff, e.g. Add New Item.

Re: Visual Studio 2017 Launch [video]

#106
post #58

Its a great sense of relief to finally ship this product, we really hope folks give it a try and join our live keynote which is streaming now at http://launch.visualstudio.com

As a newcomer to .net I was really confused by the lacking refactoring support in Visual Studio (yes, things we spoiled Java brats take for granted like extract method, extract class, move to separate file etc). Is this available in VS 2017? Edit: and live unit testing! I was looking forward to that until I found out it was only available in the enterprise version. (And yes, here you have an edge on Java anyway I thi…

Hi Eitland!

I'm a dev on the C#/VB IDE experience (and i've written and maintain many of the Refactorings for those languages). C# and VB do support refactorings like 'Extract Method' and 'Move to Separate File'.

We've also exposed a full analysis and code manipulation API through 'Roslyn' so that community members can contribute even more refactorings through extensions.

One reason this may not have been clear is that previously we didn't strongly indicate to you that a refactoring was available. i.e. when you selected some code to extract a method, you would then have to use ctrl-dot to get the list of things you could do. Now, in VS2017 we pop up our 'Lightbulb' whenever refactorings are available. This helps make the refactorings much more discoverable and we've seen a very large uptick in people invoking them now that it's much clearer that they're available.

If you use VS2017 and find issues with our fixes/refactorings, or you would like us to add more, please file feedback at https://github.com/dotnet/roslyn Thanks!

Re: Visual Studio 2017 Launch [video]

#107
post #10

Earlier quoted context omitted.

It does and can most likely be enabled by editing the vcxproj directly. Edit: something along the lines of: Edit: see response.

This is correct, take a look at https://docs.microsoft.com/en-us/visualstudio/msbuild/msbuil... and child topics on inclusion/exclusion. -eric PM, VC++ team

While it does work in the builds, the IDE is not supporting this particularly well. As another comment pointed out, changes on the filesystem are not automatically detected. Also, some IDE functionality doesn't work propetly in a project with - for example, Add New/Existing Item fails with an error.

Re: Visual Studio 2017 Launch [video]

#108
Usually a new version of VS comes with a new version of the .net framework. It doesn't seem to be the case here. I can't see the tuples announced for VB for instance.

I am getting an error with Dim p As (x As Integer, y As Integer) saying that I am missing a reference to 'System.Runtime.CompilerServices.TupleElementNamesAttribute' (but if tuples are part of the language why do I need an external reference? and this assembly doesn't seem to exist anyway). In fact right now a simple empty command line program containing nothing more than the below hangs the VS IDE completely...

  Module Module1

    Sub Main()
        Dim p As (x As Integer, y As Integer)
    End Sub

  End Module

Re: Visual Studio 2017 Launch [video]

#109
post #88

Earlier quoted context omitted.

Of course it would have helped if they made use of a std::vector like class with bounds checking enabled, instead of a pure C array. "Many years later we asked our customers whether they wished us to provide an option to switch off these checks in the interests of efficiency on production runs. Unanimously, they urged us not to--they already knew how frequently subscript errors occur on production runs where failure…

I'm still unsure of the rate at which this could be a solution to leverage checked C++ library types, and whether in the precise case of the Cloudfare issue this would be applicable. However I still think that in most case if you must handle out-of-bound conditions from a checked language outputting to an unchecked one, you just emit your checking code yourself... Also the C++ standard is 1500 pages long. I prefer to…

> you just emit your checking code yourself...

Which C programmers keep failing to do, regularly, according to the CVE database.

> Also the C++ standard is 1500 pages long. I prefer to avoid knowing that as a backend language when I can...

Which includes the libraries that C lacks.

ANSI C + POSIX isn't much shorter than that.

Re: Visual Studio 2017 Launch [video]

#110

Where did the ISO:s go? Please give us something with a known hash. I attempted to create the offline installer [1] but the vs_community.exe just silently quit after some mintues, having downloaded only some certificates. The custom download idea is easily planted with malware and all those bad things. Also, please consider upgrading from SHA-1. > We understand that a lot of customers want an offline installer for Vi…

A few quick thoughts on the topic of ISOs, to give you all a little extra context.

1. Visual Studio 2017 is a huge product, because we support so many types of development: from Android to UWP to C++ to Unity to Linux. If we were to still offer a 'full' install, it would come in at over 50GB. That's one huge ISO image!

2. We surveyed hundreds of people during the previews and RCs, and people told us that they had historically used an ISO for two reasons: (i) because they wanted to download once and create a network install for enterprise deployment; (ii) because they had a shaky internet connection and wanted to be sure they'd downloaded successfully before installing. A single monolithic ISO isn't the best solution for either of those scenarios - it's just the one that people are habituated to over all these years.

3. For the former (enterprise deployment), we have a full administrators' guide that provides detailed guidance on how to deploy the product: https://docs.microsoft.com/en-us/visualstudio/install/visual.... This includes PowerShell scripts, examples of using the installer to create and update a network cache, descriptions of how to deploy Visual Studio in a fully offline environment, and so on.

4. For the latter, we've worked really hard to improve the robustness of the installer. The componentization work we've done means that the smallest install is one-tenth the size of Visual Studio 2015, making it far more likely to succeed. And other typical installs are smaller too. We download VS in small packages that are more likely to succeed, and we use multiple ways (WebClient, BITS, WinInet) to download those files to minimize problems with AV and proxy software. If you want to download first then install, you can use the offline guide to cache just those pieces that you need, which we've just rewritten for RTW: https://docs.microsoft.com/en-us/visualstudio/install/create...

5. Because of the nature of our product (rapidly updating, lots of third-party components), an ISO is problematic. We don't have the rights to redistribute several large components (including Android), and others update on a rapid cadence that often includes critical security fixes, meaning an ISO image is incomplete, often outdated, and potentially insecure. Most customers assume that an ISO would support offline installation, but that's not true. And so we fear that offering an ISO will just creating more disappointment.

Lastly, we're listening to requests for an ISO and paying attention to the feedback we're getting; at the same time, we're hoping that this is the release where we can gently move forward to a new model that better supports delivery of developer tools at a fast, well-maintained cadence.

Hope this is useful context. And again, we're listening :)

Tim Sneath | Visual Studio Team

Post reply on HN