Debugging simple ASP.NET Core 2.1.5 template with Visual Studio 2017
Have been beating on this for a couple days now. Created a simple ASP.NET Core app using template in Visual Studio 2017 Professional with all the latest updates. When I try to debug I get this:
- I'm running VS as admin
- set the startup project correctly
- cleaned and build solution
- all packages loaded fine
- and I have been using VS for a very long time professionally.
All the "Start" options are grayed out and debug start option has "start" when it should say "IIS Express".
Tried this with several different canned templates across 3 different development machines. They all have the same problem.
Checked many posts and tried pretty much everything I can think of. I have not uninstalled everything and reinstalled yet but probably soon.
Here is where it gets strange. Loaded the "Community" Version and it works great with the same solution. Still does not in "Professional". Then created a new solution with template on my Mac Visual Studio and it also worked great.
I have VS Professional and Enterprise loaded on all three of my dev computers with same result. Making me crazy. Trying to make the switch to all the new Microsoft Core frameworks. This is my first post so be gentle;-)
c# visual-studio visual-studio-debugging asp.net-core-2.1
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
add a comment |
Have been beating on this for a couple days now. Created a simple ASP.NET Core app using template in Visual Studio 2017 Professional with all the latest updates. When I try to debug I get this:
- I'm running VS as admin
- set the startup project correctly
- cleaned and build solution
- all packages loaded fine
- and I have been using VS for a very long time professionally.
All the "Start" options are grayed out and debug start option has "start" when it should say "IIS Express".
Tried this with several different canned templates across 3 different development machines. They all have the same problem.
Checked many posts and tried pretty much everything I can think of. I have not uninstalled everything and reinstalled yet but probably soon.
Here is where it gets strange. Loaded the "Community" Version and it works great with the same solution. Still does not in "Professional". Then created a new solution with template on my Mac Visual Studio and it also worked great.
I have VS Professional and Enterprise loaded on all three of my dev computers with same result. Making me crazy. Trying to make the switch to all the new Microsoft Core frameworks. This is my first post so be gentle;-)
c# visual-studio visual-studio-debugging asp.net-core-2.1
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
add a comment |
Have been beating on this for a couple days now. Created a simple ASP.NET Core app using template in Visual Studio 2017 Professional with all the latest updates. When I try to debug I get this:
- I'm running VS as admin
- set the startup project correctly
- cleaned and build solution
- all packages loaded fine
- and I have been using VS for a very long time professionally.
All the "Start" options are grayed out and debug start option has "start" when it should say "IIS Express".
Tried this with several different canned templates across 3 different development machines. They all have the same problem.
Checked many posts and tried pretty much everything I can think of. I have not uninstalled everything and reinstalled yet but probably soon.
Here is where it gets strange. Loaded the "Community" Version and it works great with the same solution. Still does not in "Professional". Then created a new solution with template on my Mac Visual Studio and it also worked great.
I have VS Professional and Enterprise loaded on all three of my dev computers with same result. Making me crazy. Trying to make the switch to all the new Microsoft Core frameworks. This is my first post so be gentle;-)
c# visual-studio visual-studio-debugging asp.net-core-2.1
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
Have been beating on this for a couple days now. Created a simple ASP.NET Core app using template in Visual Studio 2017 Professional with all the latest updates. When I try to debug I get this:
- I'm running VS as admin
- set the startup project correctly
- cleaned and build solution
- all packages loaded fine
- and I have been using VS for a very long time professionally.
All the "Start" options are grayed out and debug start option has "start" when it should say "IIS Express".
Tried this with several different canned templates across 3 different development machines. They all have the same problem.
Checked many posts and tried pretty much everything I can think of. I have not uninstalled everything and reinstalled yet but probably soon.
Here is where it gets strange. Loaded the "Community" Version and it works great with the same solution. Still does not in "Professional". Then created a new solution with template on my Mac Visual Studio and it also worked great.
I have VS Professional and Enterprise loaded on all three of my dev computers with same result. Making me crazy. Trying to make the switch to all the new Microsoft Core frameworks. This is my first post so be gentle;-)
c# visual-studio visual-studio-debugging asp.net-core-2.1
c# visual-studio visual-studio-debugging asp.net-core-2.1
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
edited Nov 22 '18 at 2:50
Leo Liu-MSFT
19.4k22333
19.4k22333
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
asked Nov 21 '18 at 23:36
Jeff PetrieJeff Petrie
32
32
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Debugging simple ASP.NET Core 2.1.5 template with Visual Studio 2017
First, please make sure you do not have Multiple Startup Projects enabled:
Second, excluded the project from the solution and then build solution without it. Then add that project and build solution and set that project as Start Up project.
Third, if above not help you, try to restart the Visual Studio and PC, and create other project type app to check if still have this issue.
Hope this helps.
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
add a comment |
Sorry for the delay in answering this but it may help others. The answer was re-install Visual Studio 2017. I got things going on some other Dev boxes I have but last night I had the time to circle back on this problem from the original computer.
This computer had VS 2013, VS 2015 and VS 2017 installed on it. I uninstalled everything, rebooting a few times in the process and then installed the latest VS 2017. Problem solved!
I really hate when the answer is uninstall and re-install solves the problem, but sometimes that's just the answer.
Thanks Leo, you were spot on.
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53421945%2fdebugging-simple-asp-net-core-2-1-5-template-with-visual-studio-2017%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Debugging simple ASP.NET Core 2.1.5 template with Visual Studio 2017
First, please make sure you do not have Multiple Startup Projects enabled:
Second, excluded the project from the solution and then build solution without it. Then add that project and build solution and set that project as Start Up project.
Third, if above not help you, try to restart the Visual Studio and PC, and create other project type app to check if still have this issue.
Hope this helps.
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
add a comment |
Debugging simple ASP.NET Core 2.1.5 template with Visual Studio 2017
First, please make sure you do not have Multiple Startup Projects enabled:
Second, excluded the project from the solution and then build solution without it. Then add that project and build solution and set that project as Start Up project.
Third, if above not help you, try to restart the Visual Studio and PC, and create other project type app to check if still have this issue.
Hope this helps.
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
add a comment |
Debugging simple ASP.NET Core 2.1.5 template with Visual Studio 2017
First, please make sure you do not have Multiple Startup Projects enabled:
Second, excluded the project from the solution and then build solution without it. Then add that project and build solution and set that project as Start Up project.
Third, if above not help you, try to restart the Visual Studio and PC, and create other project type app to check if still have this issue.
Hope this helps.
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
Debugging simple ASP.NET Core 2.1.5 template with Visual Studio 2017
First, please make sure you do not have Multiple Startup Projects enabled:
Second, excluded the project from the solution and then build solution without it. Then add that project and build solution and set that project as Start Up project.
Third, if above not help you, try to restart the Visual Studio and PC, and create other project type app to check if still have this issue.
Hope this helps.
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
answered Nov 22 '18 at 6:12
Leo Liu-MSFTLeo Liu-MSFT
19.4k22333
19.4k22333
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
add a comment |
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
This is single project solution so confirmed startup options(as above) and have done multiple reboots during my investigations. Created several simple template solutions. They debug with the community version but not professional. Thx.
– Jeff Petrie
Nov 22 '18 at 16:09
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
It seems your professional has some issue, have you try to repair or reinstall the professional Visual Studio?
– Leo Liu-MSFT
Nov 28 '18 at 6:11
add a comment |
Sorry for the delay in answering this but it may help others. The answer was re-install Visual Studio 2017. I got things going on some other Dev boxes I have but last night I had the time to circle back on this problem from the original computer.
This computer had VS 2013, VS 2015 and VS 2017 installed on it. I uninstalled everything, rebooting a few times in the process and then installed the latest VS 2017. Problem solved!
I really hate when the answer is uninstall and re-install solves the problem, but sometimes that's just the answer.
Thanks Leo, you were spot on.
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
add a comment |
Sorry for the delay in answering this but it may help others. The answer was re-install Visual Studio 2017. I got things going on some other Dev boxes I have but last night I had the time to circle back on this problem from the original computer.
This computer had VS 2013, VS 2015 and VS 2017 installed on it. I uninstalled everything, rebooting a few times in the process and then installed the latest VS 2017. Problem solved!
I really hate when the answer is uninstall and re-install solves the problem, but sometimes that's just the answer.
Thanks Leo, you were spot on.
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
add a comment |
Sorry for the delay in answering this but it may help others. The answer was re-install Visual Studio 2017. I got things going on some other Dev boxes I have but last night I had the time to circle back on this problem from the original computer.
This computer had VS 2013, VS 2015 and VS 2017 installed on it. I uninstalled everything, rebooting a few times in the process and then installed the latest VS 2017. Problem solved!
I really hate when the answer is uninstall and re-install solves the problem, but sometimes that's just the answer.
Thanks Leo, you were spot on.
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
Sorry for the delay in answering this but it may help others. The answer was re-install Visual Studio 2017. I got things going on some other Dev boxes I have but last night I had the time to circle back on this problem from the original computer.
This computer had VS 2013, VS 2015 and VS 2017 installed on it. I uninstalled everything, rebooting a few times in the process and then installed the latest VS 2017. Problem solved!
I really hate when the answer is uninstall and re-install solves the problem, but sometimes that's just the answer.
Thanks Leo, you were spot on.
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
answered Jan 4 at 11:58
Jeff PetrieJeff Petrie
32
32
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53421945%2fdebugging-simple-asp-net-core-2-1-5-template-with-visual-studio-2017%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
