I have the latest VS2017 Enterprise.
I have 'ASP.NET and web development' workload installed.
Also I have .NET Core SDK both versions 32/64 bits.
I create new ASP.NET Core Web Application from template.
When I try to 'Start without debugging' I got an error - "The Project doesn't know how to run the profile IIS Express"
At the same time this project can be run successfully from command line
dotnet run
I know that similar question exists but all suggestions from it are not helpful in my case
Visual Studio 2015 can't start IIS Express
I reinstalled my VS from scratch and now it works
try to remove the vs folder and try to run the project
The .vs is a hidden folder so you have to enable the Show hidden files
PS: close visual studio before removing the folder
Related
I hope you all are well!
Visual Studio 2017 -
WIN-FORM -
C#
I added a Setup Project to my app.
I also selected as prerequisites SQL Server 2019 Express LocalDB:
The installer installs the app just fine but does not install the prerequisites SQL Server 2019 Express LocalDB. There are no popup error messages displayed or any in the Event Viewer.
If I download SqlLocalDB, I install it just fine and my app works. But I would like to have it install during the setup installation if it is needed (auto detect).
I tried on various computers and it also doesn't install SqlLocalDB.
I cannot find anything on the Internet that would explain why setup is not installing the prerequisites.
Any suggestion is appreciated.
Regards,
Setup projects are no more supported starting from VS 2019. So if it's a new project - you might want to try WiX toolset project. There you can add checking of prerequisites to be installed on the MSI level, or you can create your Bootstrapper bundle, which will contain installation for both SQL Server and your own app
The issue was that I was using the .MSI instead of the .EXE file to install the app. Using the .EXE did in indeed prompt the user to installSqlLocalDB.
Solution here:
when I want start my project in vs 2019 i see this error:
unable to start debugging.failures to process configuration file. try to start this application. if failures continue, try to repair your installation.
I tested in windows form application, console application and asp Core.
My project will be built but will not start from visual studio 2019.
I repair and update vs 2019 but also I have this error
Because Visual Studio is installed by an online installer, you will often run into problems. It is better to install Visual Studio with an authorized IP or find a full version of it without the need for online installation. You can reinstall vs
This error was due to incomplete installation of Visual Studio. Repair, update, or reinstall Visual Studio to resolve this issue.
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.
I have Visual Studio 2013 Ultimate. Today when I opened it, it didn't load any of my solution's projects. Error message:
Unsupported
This version of Visual Studio is unable to open the following projects. The project types may not be installed or this version of Visual Studio may not support them.
For more information on enabling these project types or otherwise migrating your assets, please see the details in the "Migration Report" displayed after clicking OK.
- ETL_<Project name>, "<Project path></Project>.csproj"
Non-functional changes required
Visual Studio will automatically make non-functional changes to the following projects in order to enable them to open in Visual Studio 2013, Visual Studio 2012, and Visual Studio 2010 SP1. Project behavior will not be impacted.
- <Project name></Project>, "<Project path></Project>.sln"
These projects are of types Class Library and Console Application. If I try to create a new project, these types are listed, but when I create it I get message <Project path> cannot be opened because its project type (.csproj is not supported by this version of the application. To open it, please use a version that supports this type of project..
So, Visual Studio is telling me it doesn't support a project it just created?! GJ M$!!
Unfortunately I was unable to solve this. I ended up uninstalling VS Ultimate. Now I use VS Express for Desktop, and it works with my old projects.
My assumption is that something on Windows broke some part of VS. I should have tried to uninstall and reinstall it but didn't have the opportunity.
I have the same thing in a Hyper-V VM. After repair did not work, I deinstalled and reinstalled VS 2017. Same thing.
In the host I can still open the same project with VS, so it is not the project, but the VS install that has a problem.
It puts this in the migration log:
src\DTOWEB\project.json: Failed to migrate XProj project DTOWEB. Could not find project.json at C:\DTOWeb\DTOWEB7\src\DTOWEB\project.json.
I have a second VM that is x86 iso x64, and it can open the project without problems. So again, my conclusion is there is nothing wrong with the project.
I cannot debugg Asp.Net 5 project in my Visual Studio 2015. First when I open app I get message box with information:
Cannot find DNX SD version 'dnx-clr-win-x86.1.0.0-beta3'.....'dnx=clr-win-x86.1.0.0-bet5' will be used as the solution DNX SDK version for this session.
Then when I click Start to debbug app I get alert box:
The debugger cannot continue running the process.Unable to start debugging.
Even when I create new project -> Asp.Net 5 preview template -> web application the behavior is the same. When I was using CTP version of VS 2015 everything worked but I had to change to VS 2015. I also cheked PowerShell version and it's 4.0.
I have no Idea what could be the reason. Any help appreciated.
I think you need to install the correct DNVM,
you can read about it here.
Or change versions of packages that you use.
Put in cmd:
dnvm list
look what SDK version is default and then set in global.json and project.json same version.