Skip to content
New issue

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

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

Already on GitHub? # to your account

Detect legacy ASP.NET Websites via project GUID #1084

Merged
merged 6 commits into from
Jan 19, 2018

Conversation

filipw
Copy link
Member

@filipw filipw commented Jan 11, 2018

This is a follow up to #1066.

I just noticed the logic there wasn't sufficient as these projects don't necessarily start with http:// - for example it could be localhost or any other string really (up to the user).

However, the legacy ASP.NET Websites have a common well-known project GUID so we can use that to exclude it from OmniSharp (since they don't have csproj files, we can't support them at the moment).

I threw in a test just to be on the safe side.

Copy link
Contributor

@DustinCampbell DustinCampbell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@filipw
Copy link
Member Author

filipw commented Jan 19, 2018

thanks - it's green now, so I will merge this to unclog the PR pipeline a bit

@filipw filipw merged commit dca4795 into OmniSharp:master Jan 19, 2018
@filipw filipw deleted the feature/legacy-asp.netwebsite branch January 19, 2018 15:24
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants