Skip to content

Conversation

@adumitr
Copy link
Contributor

@adumitr adumitr commented Feb 18, 2016

update semantics are not supported on server communication links

update semantics are not supported on server communication links
@adumitr
Copy link
Contributor Author

adumitr commented Feb 22, 2016

I would really like this to be in the next release for which we're a couple a days from the cutoff date. Can we please pull this in quicker?

@hovsepm
Copy link
Contributor

hovsepm commented Feb 23, 2016

@adumitr this approach does not let users understand why the cmdlet was removed. It would be better to throw an exception with some meaningful explanation rather than just commenting out the cmdlet which is there for several releases.

@adumitr
Copy link
Contributor Author

adumitr commented Feb 23, 2016

I see your point. We considered it, in this case we'd like for the cmdlet to not show up at all. It was never documented and it never worked before, update semantics are not allowed on the service side so the exceptions would come from there anyway. Let's merge as is

@markcowl
Copy link
Member

@adumitr @hovsepm Commenting out the cmdlet is not acceptable - you must remove the file and remove the reference from the .csproj file.

@adumitr
Copy link
Contributor Author

adumitr commented Feb 24, 2016

Okay, done, can we merge it now?

hovsepm pushed a commit that referenced this pull request Feb 24, 2016
Disable Set-AzureSqlServerCommunicationLink
@hovsepm hovsepm merged commit cf4dbdc into Azure:dev Feb 24, 2016
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.

4 participants