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

Fixed wrong application domain selected #410

Merged
merged 3 commits into from
Apr 7, 2020

Conversation

DavidEshtehari
Copy link
Contributor

@DavidEshtehari DavidEshtehari commented Feb 7, 2020

In the process of starting the listener to receive the notifications from SQL Server instance, if there is not a process dispatcher, we should obtain it first. In this process, we need the main application domain in the active process that has access to Microsoft.Data.SqlClient assembly to create an instance of SqlDependencyProcessDispatcher type.
The issue occurred when we tried to create the instance on the wrong domain.

@dnfclas
Copy link

dnfclas commented Feb 7, 2020

CLA assistant check
All CLA requirements met.

@DavoudEshtehari DavoudEshtehari changed the title Fix issue (#401) Fixed wrong application domain selected Mar 10, 2020
@dotnet dotnet deleted a comment from DavidEshtehari Mar 10, 2020
@cheenamalhotra
Copy link
Member

Uploading package for testing:
Microsoft.Data.SqlClient.2.0.0-PR410.nupkg.zip

@cheenamalhotra cheenamalhotra added this to the 2.0.0-preview3 milestone Apr 7, 2020
@DavoudEshtehari DavoudEshtehari merged commit 9190a1c into dotnet:master Apr 7, 2020
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

Successfully merging this pull request may close these issues.

SqlDependency.Start throws FileNotFoundException in Microsoft.Data.SqlClient 1.1.0
6 participants