TL;DR: Has anyone found a way to open folders in WSL2 using Visual Studio 2022?
Context: I am developing a C/C++ Linux software. Currently, I am using VisualStudio Code to open and edit source files. Now, I am way more efficient with Visual Studio 2022 and I cannot find a way to open folders inside of WSL2. (Single files work, but that is nearly not good enough for a proper workflow).
I have tried following this answer, but it does not do what I need.
Further, according to this MS devblog, quote:
"Our C++ cross-platform support in Visual Studio assumes that all source files originate in the Windows file system." This is not the case for me, my files originate in WSL2 and making them originate in Windows would be a hassle that would outweigh the benefits gained from working with VS2022.
Note: I only want to write code this way. Building and running the software is done somewhere else.
Anyone managed to make this work?
It is not possible at this moment according to https://devblogs.microsoft.com/dotnet/debug-your-net-core-apps-in-wsl-2-with-visual-studio/#comment-7947
https://developercommunity.visualstudio.com/t/cant-debug-dotnet-core-project-in-wsl/1554569
The feedback was from Oct 19, 2021. I am very disappointed.
Currently the extension only support opening projects that are stored in the windows disks (it leverages WSLs automount feature). If opening from a network location is something you need please add it as a suggestion on Developer Community.
Related
I installed Visual Studio 14. Now I have a new app VsHub in the system tray / notification area. What is it? I tried clicking and right-clicking on it, it doesn't do anything.
According to Visual Studio Blog site (http://blogs.msdn.com/b/visualstudio/archive/2014/08/18/visual-studio-14-ctp-3-released.aspx?PageIndex=2&wa=wsignin1.0):
"The Visual Studio Hub is an executable that supports multi-tool
communication across the VS family of apps, service
composition/isolation, and data/compute outside of the Visual Studio
process."
I solved stopping the folliwing Windows service:
Visual Studio Standard Collector Service
After stop, my pc is returned to work correclty, without strange load.
I hope this help you.
I have a slightly more direct solution to this. It's relatively trivial to locate where VSHub.exe and its cohorts are on your hard disk. Just go into that directory, take ownership of all the .exe files contained in it, and for each of them use "Right Click" / "Properties" / Security, and add an ACL that denies execute permissions to everyone.
Problem solved. You will need to re-do this every time you update VS 2015, but on my low power laptop, I simply can't afford the resources to keep all these unnecessary tools running. VS 2015 runs just fine without them: I can edit, build and debug programs without any problems at all.
Sure, I may be missing some of the more esoteric features of VS 2015, but for my use case YAGNI
I'm sure this is a common problem, but I can't find much info about it.
Problem
I have a work computer, a home computer, a surface, and maybe some Azure VMs that i'd like my visual studio 2013 extensions synced across them. I seem to have to refresh/wipe a computer fairly often, and re-installing all the extensions I like to use is sort of a pain. I initally thought the new VS Profiles would do this, but apparently they only sync themes/general settings.
Attempted/Outdated Solutions
There used to be an extenstion that apparently did this
Extension Sync
But that looks like it's only for VS 2010. There was also a blog post that showed the location that the extensions were saved in.
http://www.larswilhelmsen.com/2012/01/08/syncing-visual-studio-extensions-and-settings-with-dropbox/
Which looked like a perfect solution, except in 2013/2013 the extensions location must have changed, and I cannot find them.
Question
Does anyone know how I could sync my extensions across multiple machines? Or possibly know the location that the Extensions are stored in and if it's possible to change that location to something like Dropbox/Skydrive/Google Drive?
If you've upgraded to Visual Studio 2015 there's a new extension that Microsoft just released for it called the Roaming Extension Manager.
It sounds like this is what you are looking for.
https://visualstudiogallery.msdn.microsoft.com/7b421a95-c32c-4433-a2be-a41b276013ab?SRC=Home
There's something called the "User State Migration Tool" that is intended for preserving state in corporate PC desktop deployments for wipe-and-load, similar to your Azure scenario.
If you know something about the way the extension settings are saved (as shown in the blog), it's not too hard to construct an XML descriptor and use the deployment tool to apply the settings. The tool is command line so it is easily automated.
http://technet.microsoft.com/en-us/library/hh825142.aspx
This solution has increasing value when you have more than just Visual Studio to migrate into your VM.
there is new Extention for Visual Studio 2022 there which allow to import/export
Extension Manager
I am currently in the process of developing a program in Visual Basic. For now, I want to give the program to a few friends to test, make changes and then release it. But I don't exactly know how. I used the Publish feature in Visual Basic, but I don't exactly know what I'm supposed to do with it. It mentions things like installing from a disk and whatnot. I just plan to upload it to a file sharing website and release it that way.
EDIT: Using Visual Studio 2012
Use dropbox or any file sharing site :D
The purpose is to have a USB flash to have a developer seat everywhere. The idea is to use application virtualization to package Visual Studio.
However, AFAIK, there are big problems.
Have anyone succeeded in packaging Visual Studio (2010, 2008) using ThinApp, App-V, ...
P.S. I'm aware of google.
This is not possible. There's nothing "thin" about Visual Studio, it has an enormous mass of files in many different directories and a very large number of critical registry entries. Including many COM components. That it works as well as it does is one of the modern day's Seven World Wonders of software engineering.
Your license allows you to install VS on more than one machine as long as only one user uses it. I recommend you take advantage of it.
It is possible to install Visual Studio 2013 in App-V, it takes a lot of time to load and takes about 3Gb in .dat file. Compiling and debugging in C++ tested and works but really slow. No errors or popups for missing components so far. After experimenting I made a final virtualization script that works. p.m me.
It is possible to make Visual Studio portable version using VMWare Thinapp. No installation will be needed for Visual Studio, .net Framework or any other dependency. It works with Visual Studio Express edition 2008 as I have experimented but for version 2010, it say "Invalid Licence Data. Reinstall...". If you find a way, please tell me!
Our company is considering using the Visual Studio Shell for one of our products.
Does anyone have any experience using it? Was it easy to work with? Did it save time? Are there any things that you weren't able to get it to do? Have you shipped anything with it?
A couple of points regarding the Isolated shell.
As you might know, there are two considerations when you use shell - Isolated Mode and Integrated Mode. (Read more from MSDN)
Isolated Shell can be used by organizations, to build applications that run side by side with other editions of Visual Studio.
Here are some points we learned,
trying to use shell for some of our
applications.
If you are planning to use Isolated
shell, you can't use Microsoft
Language Packages like C# and VB.NET
inside that.
Creating a package for your shell is
much like creating any other VS
Package.
You don't have support for Team
Explorer and VS Built in Source
Control access, in Isolated Shell
(See this post from Vin)
Though not directly related - If you are using VS SDK 1.1 to develop your packages - remember that the managed package framework is no longer available with the default distribution. So don't get surprised if your old packages can't load MPF files after moving to SDK 1.1. It has got moved to Codeplex as a separate download.
I played around a bit with it a couple of weeks ago, like every thing there is going to be a learn curve but if you study the examples a bit and have a look at a project on codeplex called Storyboard designer. I'm sure that you could pick it up, I found it very hard to find other examples on the net but I wasn't looking very hard.
I would say if you think that the shell can give you want you need I would go for it, it is a very handy interface to work with and if your targeting developers it is also a common interface for them, so it will feel natural.
I typically use Visual Studio Community on my PC for developing business intelligence solutions (databases, SSIS, SSAS, SSRS), then deploying to the server. A few weeks ago my managers requested we put Visual Studio on a server so that other developers and consultants could connect to the server and access Visual Studio.
Ultimately I installed SQL Server Data Tools (14.0.61021.0), which automatically installed Visual Studio Shell 2015. After installation, I launched Visual Studio Shell and tried doing some of the things I am used to doing in Community edition. I was able to do pretty much anything I was used to doing for BI Development.
Visual Studio Shell 2015:
Solution files with BI projects...
SSIS
Installing extensions & add-ons...
ANKHSVN for version control with SVN server
Visual Studio 2015 Color Theme Editor
Project deployment