1615282118
In a previous post, using GitHub Actions in Visual Studio is as easy as right-click and Publish, we announced the efforts we added to Visual Studio extending our Publish experiences to introduce and assist customers into a repeatable, predictable continuous integration and deployment (CI/CD) environment using GitHub Actions. Our Publish experience today enables many different ways for developers to get their development, staging, or production apps to various endpoints in their local/network environments and directly to their cloud resources in Azure. We want to maintain that experience and offer more through Publish, providing more value to those desiring CI/CD but also introducing the ease of setup of this workflow to existing users of Publish.
As a part of our development we engaged with some of you in our Developer Community, social media, and directly through some 1:1 interactions trying out our prototypes. All of these experiences were valuable to the team to see how different users of Visual Studio – and specifically Publish – interpret and expect things to work when the option of CI/CD using GitHub Actions is available. Some of the key learnings we had from you all were:
#github #vscode
1603861600
If you have project code hosted on GitHub, chances are you might be interested in checking some numbers and stats such as stars, commits and pull requests.
You might also want to compare some similar projects in terms of the above mentioned stats, for whatever reasons that interest you.
We have the right tool for you: the simple and easy-to-use little tool called GitHub Stats.
Let’s dive right in to what we can get out of it.
This interactive tool is really easy to use. Follow the three steps below and you’ll get what you want in real-time:
1. Head to the GitHub repo of the tool
2. Enter as many projects as you need to check on
3. Hit the Update button beside each metric
In this article we are going to compare three most popular machine learning projects for you.
#github #tools #github-statistics-react #github-stats-tool #compare-github-projects #github-projects #software-development #programming
1618243440
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
1598530740
New features in Git Integration, .NET Productivity, Web Tools, and Xamarin are releasing in Visual Studio 2019 v16.8 Preview 2. Each of our teams continue to work hard to delight our developers. For this reason, Preview releases are some of the most exciting for us as we wait to hear how our newest features impact your work.
From my perspective, one of the greatest aspects of shipping releases is how engaged you are in the improvement of our products. If you have any suggestions or run into any challenges using these features, please visit our Developer Community to let us hear your perspective. If you want greater details of what’s in this release, please see our release notes.
Some repositories have more than one solution in them. Now when you open such a repository, the Solution Explorer will display a list of solutions for you to select. By default, folder view is always present at the top. This opens the root folder of the repository. Double clicking on a solution in this list will take you to that solution. Also, you can use the Switch Views button in the Solution Explorer toolbar to take you back to the list of views to easily move between solutions in your repository.
List of Views in Solutions Explorer in Visual Studio 2019 v16.8 Preview 2
In the case you have only one solution in your repository, Visual Studio will load solution view by default. On the other hand, if you have no solutions in your repository, Visual Studio will open folder view by default. You can toggle this feature on/off using its own Preview Feature checkbox in Tools | Options.
#visual studio #.net #announcement #github #visual studio 2019 #xaml
1602403391
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
1595337660
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.
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
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 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