Quickstart has broken link to Microsoft Connect

[breyed]

The following Quickstart text has a broken link:

Note: when you need to pass the mock for consumption, you must use the mock.Object accessor as a consequence of a C# compiler restriction (vote to get it removed at Microsoft Connect)

[kzu]

You can trivially edit it and send a PR with a fix right from the web ;)

/kzu from mobile

On Mar 4, 2015 4:45 PM, "Edward Brey" notifications@github.com wrote:

The following Quickstart https://github.com/Moq/moq4/wiki/Quickstart
text has a broken link:

Note: when you need to pass the mock for consumption, you must use the
mock.Object accessor as a consequence of a C# compiler restriction (vote
to get it removed at Microsoft Connect
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=318122
)

Reply to this email directly or view it on GitHub
#159.

[breyed]

I don't know what the correct URL would be.

[kzu]

Connect is dead, so we might as well just delete the thing :)

/kzu from mobile

On Mar 4, 2015 9:40 PM, "Edward Brey" notifications@github.com wrote:

I don't know what the correct URL would be.

Reply to this email directly or view it on GitHub
#159 (comment).

[breyed]

Connect is not dead. I can log into the dashboard and see the dozen bugs I've reported that they've fixed and more importantly my 11 bugs that are still active (examples: 1, 2, 3).

Perhaps you are referring to suggestions, which used to be hosted on Connect, but have since moved to UserVoice. Do you know if the compiler restriction referred to is one of these?

[stakx]

I cannot find the issue on the search page you mentioned.

The feedback in question must have been about allowing implicit conversions from Mock<T> to T so one wouldn't have to write mock.Object, one could just let C# so an implicit conversion.

I assume that these days, one would ask for C# / VB.NET language features over at https://github.com/dotnet/roslyn/issues. Unfortunately, they currently have over 3,000 open issues. If anyone can track down a Roslyn issue that, if followed up on, would enable Moq to drop the mock.Object workaround, please report the issue link here.

In the meantime, perhaps it would really be best to just remove the broken link from the quickstart page.

[kzu]

yep, +1 to removing it

On Sun, Jun 4, 2017 at 3:29 PM stakx ***@***.***> wrote: The feedback in question must have been about allowing the definition of an implicit operator T where T can be an interface. Which would be useful to Moq because it would mean you don't need to say mock.Object, instead the Mock<T> could just be passed to anything that expects a T an the implicit type conversion operator would bridge these types. I assume that these days, one would ask for C# / VB.NET language features over at https://github.com/dotnet/roslyn/issues. Unfortunately, they currently have over 3,000 open issues. This one <dotnet/roslyn#14186> might come somewhat close. Perhaps it would be really best to just remove the broken link, at least for the time being. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#159 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKW6-yT_hi6HrH876peOi-5_qC5JRtUks5sAveGgaJpZM4DplcX> .

--

…

-- /kzu from mobile

[stakx]

Will do.

[stakx]

Done.