Visual Studio Codespaces Is Now GitHub Codespaces

Earlier this month, Microsoft announced that Visual Studio Codespaces is consolidating into GitHub Codespaces. Visual Studio Codespaces is a cloud-based, on-demand development environment similar to Gitpod. The consolidated product supports Azure Functions and can be used with Visual Studio 2019, Visual Studio Code, and modern browsers.

Originally released as Visual Studio Online at last year’s Microsoft Ignite, Visual Studio Codespaces is an online, cloud-powered development environment. It embraces DevOps concepts and provides managed, fully configurable, disposable environments that can be shared and replicated as needed. According to Microsoft, the consolidation into GitHub Codespaces aims to eliminate the need to transition from a repository to a codespace, an issue identified among Visual Studio Codespaces users since its first release in April this year.

The idea of a DevOps-enabled online development environment is also behind GitPod, launched a few weeks before Visual Studio Codespaces. In the official product blog, Sven Efftinge, co-founder and CEO of Gitpod, describes Continuous Development Environments as the “missing piece” in DevOps:

Continuous dev environments are a crucial part in a fully optimized DevOps toolchain, that allow to instantaneously spin up a ready-to-code development environment from any git state. Continuous dev environments reduce friction in onboarding and task switching and improve reproducibility across the project.

With GitHub Codespaces, developers can set up a containerized and customizable VS Code environment directly from a GitHub repository. Once the environment is created, it can be accessed through a browser or Visual Studio (VS Code or VS 2019). Since the online IDE is based on VS Code, the Visual Studio Code Marketplace can be accessed from a codespace, allowing any available extensions to be loaded and launched from the environment. It also supports multiple programming languages, Dockerfiles, LiveShare, and deployment to Azure using GitHub Actions.

#visual studio 2019 #.net #visual studio code #github #development #devops #news

What is GEEK

Buddha Community

Visual Studio Codespaces Is Now GitHub Codespaces

Earlier this month, Microsoft announced that Visual Studio Codespaces is consolidating into GitHub Codespaces. Visual Studio Codespaces is a cloud-based, on-demand development environment similar to Gitpod. The consolidated product supports Azure Functions and can be used with Visual Studio 2019, Visual Studio Code, and modern browsers.

Originally released as Visual Studio Online at last year’s Microsoft Ignite, Visual Studio Codespaces is an online, cloud-powered development environment. It embraces DevOps concepts and provides managed, fully configurable, disposable environments that can be shared and replicated as needed. According to Microsoft, the consolidation into GitHub Codespaces aims to eliminate the need to transition from a repository to a codespace, an issue identified among Visual Studio Codespaces users since its first release in April this year.

The idea of a DevOps-enabled online development environment is also behind GitPod, launched a few weeks before Visual Studio Codespaces. In the official product blog, Sven Efftinge, co-founder and CEO of Gitpod, describes Continuous Development Environments as the “missing piece” in DevOps:

Continuous dev environments are a crucial part in a fully optimized DevOps toolchain, that allow to instantaneously spin up a ready-to-code development environment from any git state. Continuous dev environments reduce friction in onboarding and task switching and improve reproducibility across the project.

With GitHub Codespaces, developers can set up a containerized and customizable VS Code environment directly from a GitHub repository. Once the environment is created, it can be accessed through a browser or Visual Studio (VS Code or VS 2019). Since the online IDE is based on VS Code, the Visual Studio Code Marketplace can be accessed from a codespace, allowing any available extensions to be loaded and launched from the environment. It also supports multiple programming languages, Dockerfiles, LiveShare, and deployment to Azure using GitHub Actions.

#visual studio 2019 #.net #visual studio code #github #development #devops #news

Visual Studio Codespaces is consolidating into GitHub Codespaces

At the last Ignite, we announced the public preview of Visual Studio Codespaces and shared our vision for cloud-powered development environments that would enable developers to work from anywhere and on any platform. Since then, we’ve seen incredible validation and excitement about codespaces and the scenarios they enable. We’ve also shipped dozens of enhancements, adjusted to better align with your expectations, and amassed feedback to help inform our roadmap. A key piece of this roadmap was partnering with our friends at GitHub to provide a native experience using the same service that powers Visual Studio Codespaces. Today, we’d like to share some news regarding this partnership: Visual Studio Codespaces will be consolidating into GitHub Codespaces.

If you’re an existing Visual Studio Codespaces user, you can start your transition to GitHub Codespaces now and the current Azure offering will be retired in February 2021.

Why is the service moving?

During the preview we’ve learned that transitioning from a repository to a codespace is the most critical piece of your workflow and the vast majority of you preferred a richly integrated, native, one-click experience. Since GitHub is the home of 50M developers, it made sense to partner with them to address this feedback. However, after the GitHub-native experience was released, we started hearing that the two distinct experiences were causing confusion amongst our users.

We believe that by consolidating the current Codespaces experiences into one, we can eliminate confusion, simplify the experience for everyone, and make more rapid progress to address customer feedback.

What does this mean for users in the public preview?

For current users, we encourage you to migrate to GitHub Codespaces with us. Since GitHub Codespaces is still in a limited public beta, we will be working to get you added to the beta as quickly as possible. The next time you connect to a codespace through the portal or Visual Studio Code, we’ll prompt you to submit the preferred GitHub account you’d like to be added to the beta. Every Azure subscription owner with a Visual Studio Codespaces plan will also receive an email requesting their preferred GitHub account.

While GitHub Codespaces provides an optimized creation experience for GitHub repositories, you can still utilize Git repositories hosted elsewhere (e.g Azure Repos, Bitbucket) with a few extra configuration steps. Check out our FAQs for more details.

#cloud #visual studio #visual studio codespaces

[Guest post] Learn C# with Visual Studio, Visual Studio for Mac, and Unity

UPDATE: The book giveaway challenge is complete. We will be announcing winners on the Visual Studio blog within the next week. Thank you for your submissions!

Visual Studio is an amazing development tool. But Visual Studio and Visual Studio for Mac are more than just intuitive, state-of-the-art development environments. They’re also remarkably powerful learning and exploration tools, with features to help you create and understand your code. I love teaching and learning about C## with Visual Studio. That’s why my co-author, Jenny Greene, and I put Visual Studio and Visual Studio for Mac right at the center of our latest book, _Head First C# _(4th edition), published by O’Reilly Media. _Head First C# _incorporates Visual Studio directly in the learning. combining Visual Studio with the unique and innovative “brain-friendly” Head First approach to teaching helps us make learning C## easier and more fun for our readers.

#visual studio #c# #unity #visual studio 2019 for mac #visual studio for mac

Writing Visual Studio Extensions with Mads - Episode 1: Item Templates

Join Mads Kristensen from the Visual Studio team each week as he builds extensions for Visual Studio live!

#visual studio code #visual studio #code #microsoft #visual studio extensions

Visual Studio 2019 v16.7 Preview 2 Available Today!

C++ Updates

Visual Studio v16.7 Preview 2 delivers various improvements in the C++ space. Within the Connection Manager, you’re now able to edit remote SSH connections, e.g. if the IP address of your target system changes and needs to be updated. You’re also able to set default remote connections to be consumed via **${defaultRemoteMachineName} **in CMakeSettings.json and launch.vs.json.

When you edit a remote connection, Visual Studio will no longer need to recopy headers to Windows for a native IntelliSense experience. Likewise, setting default remote connections is useful for checking CMakeSettings.json and launch.vs.json into source control with no user or machine-specific information. These remote connections over SSH allow you to build and debug your C++ projects on a remote Linux system directly from Visual Studio.

C++ Add or Remove SSH Connections with Connection Manager

This release also brings enhanced IntelliSense support for Clang on Windows (clang-cl) in Visual Studio. The clang include path now includes the clang libraries, we’ve improved the display of in-editor squiggles (particularly when using the std library), and we’ve added support for C++2a is supported in clang mode.

The Preview release also contains four new code analysis rules to incorporate additional safety features into C++: C26817, C26818, C26819, and C26820. Please see the C++ Team Blog for more info.

In addition, new C++20 Standard Library features have been implemented. A detailed list is provided in the STL Changelog on GitHub.

.NET Productivity

Quick Info now displays the diagnostic ID along with a help link where you can easily navigate to our documentation to learn more about warnings and errors in your code.

Diagnostic ID with help links in .NET Productivity

Git Productivity

We continue to release more Git functionality in Visual Studio 2019. This time we focus on merge conflict resolution. We’ve revamped the Visual Studio merge editor by decoupling it from TFVC and focusing it on Git.

A new gold info bar at the top of a file will tell you when there are merge conflicts that need to be manually resolved. Clicking will take you to the merge editor, which now has more informative tiles and captions to help you distinguish between the conflicting branches. We’ve reduced the clutter around the zoom margin, health margin, and the toolbar. In addition, it is easier to parse conflicts with aligned matching lines, word level differences, and visible whitespace when it is the only difference. You can turn off non-conflicting differences to just focus on the conflicts. You can also resolve add/add conflicts at the file level now with a two-way merge. Finally, we have added a checkbox to resolve all conflicts on one side or the other with a single click.

Try the new features by toggling the Preview Feature for New Git user experience in Tools > Options.

Improved Git Functionality in Visual Studio 2019 under the Tools Menu

In other Git improvements, we will now close any open folders or solutions before starting a new clone operation, so that Visual Studio can open the newly cloned repo to help you get to your code faster. We’ve improved upon the commit text box, adding inline error checking. And we’ve added UI to help you more clearly understand what is happening when you initialize and push a repository to a remote host like GitHub or Azure Repos.

Local Process with Kubernetes

Local Process with Kubernetes allows you to write, test and debug your .NET code on your development workstation while connected to your Kubernetes cluster with the rest of your application or services. By connecting your development workstation to your cluster, you eliminate the need to manually run and configure dependent services on your development machine. Environment variables, connection strings and volumes from the cluster are available to your microservice code running locally.

For more information on Local Process with Kubernetes, we have detailed it out in our team blog.

#visual studio #announcement #visual studio 2019 #visual studio code