When running Visual Studio 2022 (after upgrading from VS 2019), the four "rogue" hub-server background tasks listed below in yellow won't stop. What are they for and how do I stop them?
I'm running Visual Studio 2022 version 17.1.5.
Well, the fix to this particular problem is to logout of Visual Studio 2022 then re-log back in again.
When I upgraded to Visual Studio 2022 from VS 2019, I was already logged into my Visual Studio "Hub" account. But somehow that "rolled over" login didn't sit right with the new VS install and Hub servers. Logging out, then re-logging in again cleared that problem.
I'm just guessing, but perhaps there's an authentication issue with re-using an existing login between major VS releases. If so, then the new install should have forced a password re-entry.
Related
We have a development VM (Windows Server 2016 Standard) with some apps installed such as Visual Studio 2019 and SQL Server Management Studio 18.6. Our weekly security scans are showing that .NET Core 2.1.30 is installed, which is at end of life and should be removed. I manually uninstall the application from the apps and features control panel, but it mysteriously appears again about a month later. When I was looking at the event viewer while trying to track down who could be installing it, I notice that it is installed by the SYSTEM user. Is there any dependent app that could be reinstalling this automatically after I manually remove it?
Microsoft Visual Studio 2017 Enterprise Isolated Shell project template missing ?Any clue if i missed any extension pack pack or individual workload while installing ?
At the time of this writing (April 10, 2017) the Visual Studio 2017 Isolated / Integrated Shells haven't been announced yet. It seems that Microsoft will provide them but they need time to accommodate to the new Visual Studio 2017 internal component structure and setup. As you may know, Visual Studio 2017 doesn't use GAC or normal Windows Registry (it uses a private Registry hive) and its setup is based on workloads and very granular individual components. For example, the standalone Visual Studio 2017 Team Explorer was announced last week, weeks after the initial launch of Visual Studio 2017 RTM. With the Shells the same will happen eventually.
And now 3 years later (March 2020), it looks like Microsoft gave up on the Isolated Shell for Visual Studio. I could not find an official retirement of the software, however 2015 is the latest version I have found any reference to.
http://www.visualstudioextensibility.com/2017/04/11/microsoft-the-visual-studio-shells-and-the-old-versions/
https://visualstudio.microsoft.com/vs/older-downloads/isolated-shell/
https://visualstudio.microsoft.com/vs/older-downloads/
I am facing very weird problem. I just installed from asp.net . first it installed Microsoft Web Platform Installer and then VS13 but I had cancelled that for some reason. But studio was present under control panel > programs and was not present in start menu. I uninstalled both and installed again but I am again facing same problem. It is present in control panel but not in start menu. How can I work for it?
My Lord... It was there with the name VS Express 2013 for web.
One thing that I've noticed after installing Visual Studio 2013 Pro, was that it did not install into Program Files as "Microsoft Visual Studio 2013", but "Visual Studio 2013". It might be there if you scroll down a bit...
I've got Visual Studio 2010 Ultimate edition on my machine, and I've been working with ASP.NET a lot (my job). I recently installed Visual Studio 2012, to test it out. Noticed that I had a few issues with VS 2010 after installing VS 2012, with Unit Testing etc.
Anyway, I have been debugging & testing the ASP.NET pages in 2012 to test it out. Went back to debug and test on VS 2010 and that's when it all went wrong! Sometimes it debugs, most of the time it doesn't, and when it does the layout and formatting is horribly wrong.
Tried the ASP.NET project on my employee's machines, and it runs fine and the layout is all correct. (They use VS 2010)
I've uninstalled VS 2012 completely and tried debugging and testing in VS 2010 and I still have the same issue! I also have re-installed VS 2010 twice, and yet it still does not work.
Anybody know whats wrong with it? Or what else I can do to ensure VS 2010 and 2012 stuff has been properly uninstalled before I try another re-install?
Thanks for your time..
Create a Virtual Machine and install VS2010. In a clean install, it should work fine. Otherwise, VS2012 could have made some changes to your code. I wouldn't discard it -¿config files? ¿a new version of the bundled web server? ¿a new functionality?-.
Once you have discarded code changes due to the new version, give a try to your preferred uninstall software and delete VS2012...
Not exactly a programming question in the technical sense, but it's impacting my development nonetheless and I'm hoping someone here might have encountered and solved this issue before.
I recently got adventurous and installed Office 2010 beta onto my PC here, and I've noticed that Visual Studio has begun to hang whenever I'm editing an ASPX file, sometimes right away, sometimes after a few minutes. In my research I came across this post:
http://abdullin.com/journal/2009/5/12/visual-studio-2008-locks-or-freezes-in-aspx.html
It seems to imply that there's a dependency between Office and Visual Studio. Is anyone here successfully running Office 2010 64-bit with Visual Studio 2008? I'm on Windows 7 64-bit, also.
Josh
Edit: I have confirmed that the Setup.exe file referenced in that post is in fact being run by VS. It is indeed a vestige of the Office 2007 suite. I moved the directory it was in, and (of course) the process isn't spawned, but VS hangs on "loading cache" on this project. I think I'm getting closer though.
Hope this helps:
http://blog.hinshelwood.com/archive/2009/07/19/office-2010-gotcha-2-visual-studio-2008-locks.aspx
Unfortunately, doing a repair install of the Office-based Visual Web Developer component wouldn't work — the setup application kept crashing. I ended up solving this problem by doing a complete reinstall of Visual Studio. For some reason, doing a simple repair wasn't possible — the VS setup kept crashing, too.
I did a manual remove using an uninstall tool designed for the VS2008 RC. It did a complete install of all VS components, after which point I reinstalled VS2008, which in turn reinstalled the Office-based visual web developer component.
It was a long and painful process, but it worked. It didn't seem to be a direct incompatibility between Office 2010 and VS2008, as we have another PC here with the same combination that wasn't having the problems. I believe it had to do with the fact that my PC originally had Office 2007, which I had to uninstall before installing Office 2010. The other PC that wasn't having this problem never had Office 2007. I can only assume that the uninstall process for Office 2007 either removed those Visual Web Developer components or removed dependencies that were originally put in there by the VS2008 setup program.
office 2010 runs on wpf and its major portion is build on dotnet framework. And there is always connectivity between office and vs coz vs can make office apps also. If you use office 2010 as your default for aspx page editor and vs is also opened with the same project. it will sometimes hang due to lack of resources and also vs 2008 was made for 32bit os, so if ur running it on 64bit os with office 2010 64bit it can sometimes cause problem of resouce management. Already wpf uses hell lot of resouces and then 32bit vs 2008' connection to it will use more resouces.
So what i suggest is try to use 32bit 7, 32bit office 2010 ans vs 2008.
Regards,
Apurva