I have a multiple project solution in Visual Studio 2013. I'm not sure what caused it, but now when I click run, it runs a different project from the one I currently have set as the StartUp project. The project I'm trying to run and the project visual studio runs instead both work and CAN run. The problem occured when I booted up Visual Studio 2013 today I don't believe much has change since I last ran the project either, as I ran it yesterday.
I've tried closing and opening Visual Studio 2013, resetting my project as the StartUp project, right-clicking -> Debug -> Start new instance. All these did not fix the problem though.
SOLUTION: Rebooting my machine fixed the problem, I have no idea...
Related
I have tried the different solutions below but still facing the same issue can you please help on this how can we resolve it.
By removing the .vs folder with the respective project.
By unloading the project and editing removing the below lines of code and saving project changes like below.
By Following with the iisreset command
Repair and reinstall visual studio and IIS express
By setting control panel >> system >> advanced settings >> Environment variables.
I have tried all solutions but still getting the same issue as below.
I have gone through some references followed below. but still, the issue is not fixe
Process with an ID #### is not running in visual studio professional 2013 update 3
Visual studio 2017 process with an id of is not running error
https://www.codeproject.com/Tips/1029540/Solved-Process-With-An-Id-Of-Is-Not-Running
I met the problem in VS 2022. My solution was:
open the property of the csproj,
set build -> target plattform from "Any CPU" to "x86"
I have a WinForms application. I see the solution file, but when I try to add new project to it and select the needed type of file, after pressing "OK" nothing happens, any ideas why?
Visual Studio Professional 2017 15.4.0
UPDATE:
As it turned out I couldn't even create any empty project, so I had to reinstall visual studio cause I didn't find any other solution. All works fine now.
I've Visual Studio 2017 community edition. I have a C# project created using Visual Studio 2015. When I try to open the project in VS 2017 I get an error message prompt:
--------------------- Microsoft Visual Studio
Project 'dataStructureInCSharp' could not be opened because the Visual C# 2017 compiler could not be created.
Please re-install Visual Studio.
--------------------------- OK
I'm trying to obtain help if anyone else has faced similar issue. I feel going the uninstall and then reinstall route is very costly for me and would try that option last if I've got no other resort.
What I've done so far :
Tried starting visual studio with administrative privileges
But problem remained same.
I tried creating a new console project solution from scratch but in that case I get very same error and an additional error error also shown below:
System Environment: Windows 7 Ultimate Service Pack 1
You can try to close all VS 2017 instances and delete the folder %localappdata%\Microsoft\VisualStudio\15.0_xxxx\ComponentModelCache, then open VS to create a new Console project.
Or
please re-run the VS 2017 installer as administrator, click the icon beside ‘Launch’ button and choose ‘Repair’ to repair as shown below:
Just to brief the history of my problem, I had first installed Visual Studio(VS) 2017 community when it was in RC stage. This was first time when I saw the workload based UI of visual studio installation. Initially I simply chose .Net desktop development workload to get started as I was interested in creating only console applications to get my hands dirty.
Initially it was all working well. One fine day I added all other workloads I was interested in namely Universal Windows Platform Development, Azure Development, ASP.NET and web development,Node.js development, and Mobile development with .Net. I'm not sure if there any of the specific workloads to be blamed for the issue I've posted.
Just to avoid the case if RC and RTM release builds might not have messed up my entire environment, I simply uninstalled the entire stuff, rebooted my machine and installed it again from scratch from latest RTM release for Visual Studio Community.
I would strongly recommend that you first try possible solutions suggested by #Sara-MSFT before doing clean reinstall just in case if it works. It can save you couple of hours required in whole reinstallation process if it works.
Having recently updated from Visual Studio 2015 to 2017, I ran into a referencing issue where performance testing namespaces and dll references seem to have disappeared.
I finally figured out what had caused it, but figured a few people may run into this, so I will also be including the solution.
To solve this you have to first load up visual studio installer (It's installed alongside Visual Studio 2017) and click on modify.
Then click on Individual components and select the items shown in this image:
Microsoft test manager
testing tools core features
Web performance and load testing tools
Make sure you restart VS 2017 after installing these, I had to do a clean and rebuild as well.
After finishing my C# application I had to make an installer. After seeing that the default installer projects are gone, i searched for a replacement.
I found the Visual Studio Installer Projects. I downloaded the file from here: https://visualstudiogallery.msdn.microsoft.com/9abe329c-9bba-44a1-be59-0fbf6151054d.
When i restarted Visual Studio, opened my project, clicked "add new project" and here is what I got:
Problem is that I cant find the setup project. I have tried repairing the install. I restarted Visual Studio several times.
My Question:
How can I find the installer project and why it's not working for me.
If I cant make it work, are there any alternatives ? (except InstallShield)
Additional info:
Visual Studio 2013 Community with update 4
Windows 8.1 64-bit
You could try Tools > Extensions and Updates and search for it:
Visual Studio setup projects no longer ship with Visual Studio
However, you can download them here.
Or use a third party library like WiX.
I had the same problem and it turns out that visual studio removed the support for installer projects in 2010.
but still you can download and install it in your version
VS2013
VS2015
VS2017