Skip to content

ASP.NET Core Web API: Server fails to start due to invalid app.config file #1520

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

Closed
pfedotovsky opened this issue May 30, 2016 · 2 comments
Closed

Comments

@pfedotovsky
Copy link

pfedotovsky commented May 30, 2016

I want to consume WCF service within my ASP.NET Core Web API application. I've added needed endpoints and another configuration into the app.config file, but when I run "dotnet publish" produced .exe.config file is incorrect, see below. So I can't run project until I fix the file manually and I can't run project inside Visual Studio due to this bug.

  </system.serviceModel>
</configuration>m.serviceModel>  

</configuration>

The last N symbols is duplicated for some reason - seems to be a bug in the dotnet command-line utility.

I've created sample project to reproduce the problem: http://github.com/pfedotovsky/aspnet-tests
Just run dotnet publish and open AppConfigIssue.exe.config in the output directory.

@davidfowl
Copy link
Member

@pfedotovsky
Copy link
Author

jkotalik pushed a commit that referenced this issue Nov 1, 2018
ryanbrandenburg pushed a commit that referenced this issue Nov 22, 2018
…d tests.

#1443 Block unsolicited wsfed logins by default.
#1520 Update WsFed to use the 2.0 event structure
#1425 Implement WsFed remote signout cleanup
Rework WsFed RemoteSignOutPath logic to work with ADFS #1581
Update versions, dependencies.
@ghost ghost locked as resolved and limited conversation to collaborators Dec 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants