Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't run the website #8

Closed
MaherJendoubi opened this issue Sep 23, 2016 · 21 comments
Closed

Can't run the website #8

MaherJendoubi opened this issue Sep 23, 2016 · 21 comments
Assignees

Comments

@MaherJendoubi
Copy link
Contributor

MaherJendoubi commented Sep 23, 2016

image

@jimmyca15
Copy link
Member

This appears to be a continuation of #1. Did you run the Configure-DevEnvironment.ps1 script mentioned in the readme?

@jimmyca15 jimmyca15 self-assigned this Sep 23, 2016
@MaherJendoubi
Copy link
Contributor Author

@jimmyca15 no but I get this message
image

@jimmyca15
Copy link
Member

Oh thanks for finding that. The issue is that it is trying to invoke a script that had its name changed from constants.ps1 to globals.ps1. I will make the fix.

@jimmyca15
Copy link
Member

The issue with the development setup script was fixed in the latest commit. You should be able to run it and then run the api from visual studio.

@MaherJendoubi
Copy link
Contributor Author

image

@jimmyca15
Copy link
Member

jimmyca15 commented Sep 23, 2016

Looks good. You should be a member of the IIS Administrators group now and the error you were getting from launching from VS should be gone.

@MaherJendoubi
Copy link
Contributor Author

Jimmy I still have the same error

@MaherJendoubi
Copy link
Contributor Author

image

@jimmyca15
Copy link
Member

Can you confirm that you are in the IIS Administrators group and try running without debugging? If that is true then this could be an issue in the Visual Studio tooling that is launching the process.

@MaherJendoubi
Copy link
Contributor Author

I am in the IIS Administrators group.

@MaherJendoubi
Copy link
Contributor Author

image

@jimmyca15
Copy link
Member

The script should have fixed that.
In "<SolutionRoot>.vs\config\applicationHost.config" change

       <section name="anonymousAuthentication" overrideModeDefault="Deny" />
       <section name="windowsAuthentication" overrideModeDefault="Deny" />

to

      <section name="anonymousAuthentication" overrideModeDefault="Allow" />
      <section name="windowsAuthentication" overrideModeDefault="Allow" />

This should be done automatically in a future version of the VS tooling.

@jimmyca15
Copy link
Member

I will try to reproduce your issue. The error should be gone if you remove the windows authentication requirements from the web.config for the Microsoft.IIS.Administration project.

@MaherJendoubi
Copy link
Contributor Author

Let me give you more context:

  1. I forked your project and I updated to 1.0.1 as mentioned in my PR Updated to ASP.NET Core 1.0.1 #10

  2. even ".vs\config\applicationHost.config" change doesn't fix the problem.

  3. I suspect that the main problem is due to the tooling 1.0.1 Unable to start process aspnet/Tooling#779

@jimmyca15
Copy link
Member

I see. If you want to run the application you can remove the Windows Authentication requirements from the web.config then the tooling should no longer have an error connecting to the dotnet process. I will still investigate this to make sure there isn't another problem.

@MaherJendoubi
Copy link
Contributor Author

image

@jimmyca15
Copy link
Member

jimmyca15 commented Sep 24, 2016

I just cloned the project and ran it on a separate machine. I was originally getting the same error you were

image

then I ran the Configure-DevEnvironment.ps1 script. After that I got this error, probably because the group settings the script just altered had not propagated through to VS.

image

I restarted visual studio. After that the error went away and I was able to debug.

@MaherJendoubi
Copy link
Contributor Author

I did the same steps you did but I still having this error :
image

@MaherJendoubi
Copy link
Contributor Author

Jimmy there is something weird on my Visual Studio, I can't start debugging any asp.net core app :(

@MaherJendoubi
Copy link
Contributor Author

@jimmyca15 I have this issue now #11

@jimmyca15
Copy link
Member

Debugging for the application is working now so I'm going to close this issue.

yaqiyang added a commit that referenced this issue May 25, 2022
* Remove WebApi shim

* Replace httpget with httpget id

* Fix API controller base class

* Fix the installer after removing WebApiShim

* Clean up readme.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants