Henry

My feedback

  1. 393 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    20 comments  ·  Visual Studio IDE » IDE and Editor  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    No. Do not add a soon to be unsupported, alpha, experimental language to VS.

  2. 2,176 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    172 comments  ·  Visual Studio IDE » Install  ·  Flag idea as inappropriate…  ·  Admin →

    Thanks for the many comments on this topic. We are listening…

    On behalf of the Visual Studio team, I wanted to share a few responses to some of the questions and concerns raised, in the spirit of sharing with transparency the reasons that led us to the current installer options.

    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!

    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…

    Henry commented  · 

    Essentially saying "My room is too dirty to clean up. I don't know where to start." is not acceptable.

    Like it or not, Visual Studio installer complexity cannot be solved outside of Microsoft.

    VS core would be a good place to only install the most basic components of VS. Any add-ons would need be downloaded and installed outside of the VS installer.

  3. 36 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    No. Build a c# class instead. Generics for properties would solve this as well.

  4. 477 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    21 comments  ·  Visual Studio IDE » Languages - Visual Basic  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    The VB6 runtime is a single large component which is supported by MS. Getting a VS version to support VB6 code, drag and drop UI editing, handling all of the third party com add-ins, etc. would cost much much more.

    Porting a 16 bit friendly Visual Studio 6.0 from 1999 to a 64 bit 2017 is essentially the main work in this request.

    Too time consuming, too expensive and unlikely to ever be profitable for Microsoft.

  5. 2,308 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    33 comments  ·  Visual Studio IDE » Languages - C#  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    No, if it only supports DirectX. OpenGL based solutions are far more widespread.

  6. 2,817 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  149 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    No. Let an open source solution be carried forward. XSLT is a standard but used by a tiny subset of Visual Studio solutions. Microsoft should concentrate on more widely used tools/standards.

    Microsoft can consider committing 1 to 2 persons full time to get a viable XSLT open source solutoin going on GitHub.

    Open sourcing the legacy XSLT c code from 15+ years ago is not a viable solution for Microsoft.

  7. 2,954 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    111 comments  ·  Visual Studio IDE » Install  ·  Flag idea as inappropriate…  ·  Admin →

    I wanted to update the status to make sure you know that we hear you. This isn’t straightforward to deliver for obvious reasons: Visual Studio installs a disparate variety of tools, runtimes and SDKs, many of which come from third parties or other parts of Microsoft. We recognize that developers would love to see something lighter and while we have nothing new to announce at this stage, we are spending a lot of time thinking about how we can improve Visual Studio installation.

    Thanks for the feedback!

    Tim Sneath | Visual Studio Team

    Henry commented  · 

    Can we get VS to download all required components to a directory tree, then quit installation? Later, the user could install VS and the required compnents as needed.

    The current mix of some on the local drive, some dynamically downloaded is not a long term solution since VS 2017 install will break with a missing component URL or bad file ~5 years after VS 2017 is released.

    We have VS 2010, 2012, 2015, and 2017 solutions in our large corporation. The VS 2010 and 2012 solutions are either slated for retirement or large redevelopment in the next 2 years.

    We do not upgrade all of our solutions to the latest Visual Studio version every time. Doing so would be a full time job for 20+ developers.

    Microsoft's customers are the businesses; which have a portfolio of business software solutions to use and support. It's the first point to be noted. Cool tools for individual developers is not the focus of a business.

  8. 4,982 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    89 comments  ·  Visual Studio IDE » Project  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    It's been 15+ years in Visual Studio. Can't this be achieved?

  9. 6,174 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    107 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    No. Microsoft will not spend millions of dollars vetting all of the Silverlight source code and releasing it as open source.

    Pretending that it costs $0 is a non-starter.

  10. 11,267 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  512 comments  ·  Visual Studio IDE » .NET  ·  Flag idea as inappropriate…  ·  Admin →
    Henry commented  · 

    - Does not require store apps for Windows or Mac
    - Object serialized on one platform can be deserialized on any other platform without extra work or loss of floating point number or integer number precision
    - Development tools, libraries, packaging, etc should be runnable and able to build production applications without accesssing a third party store, web service, etc. This is needed for any realistic long term support policy. I should be able to rebuild and redeploy a product 5+ years in the future after its first release.

    Software escrow is an important part of large scale commercial software enterprise solutions.

    Reliance on 25 different third party or second/third tier MS libraries is a failure risk 2+ years after the first production release.

    A $1+ million budgeted project with a lifespan of 7+ years for corporate document retention requirements is unlikely to include any short-lived, 2-3 year, components.

    As said elsewhere, 2 to 3 developers, a github repository, message base and few random blog posts does not make for a reliable and long lived component.

Feedback and Knowledge Base