F.Y.I.: shut out at Microsoft Connect ... need to "use the mock.Object accessor"

[gerry_lowry (alliston ontario canada (705) 250-0112)]

The page urges http://code.google.com/p/moq/wiki/QuickStart

"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 **

F.Y.I.: if one signs in (at ** above), one can "Vote as important/not important".
However, the issue is marked as "Closed as Won't Fix".

------------------------------------------------------------------------
Posted by Microsoft on 04/02/2008 at 11:47 AM
Thanks for the suggestion for Visual Studio 2008!

We are doing our feature planning now for the next version of the C# language
and will soon be investigating all of our active language suggestions.
If you have any further information about this suggestion, please add a comment.

Alex Turner, Program Manager, Visual C# Compiler
------------------------------------------------------------------------
Posted by Microsoft on 24/04/2008 at 4:43 PM
Thanks again for your suggestion.
After having done feature planning for the next release of C#
I regret to say that this feature is not being added.
We have to do some harsh prioritization, both because of
our implementation and testing resources, but also because
we need to keep the number of new language features
at a manageable level - depending on how you count,
we are adding only four language features to C# this time around.
Unfortunately many great suggestions just can't make it in because of that.

I apologize that this is a "canned" follow-up answer, sent out as a result
of our feature planning for the next release. In most cases I or someone
else already replied individually to your suggestion - please let us know
if you feel it hasn't been adequately addressed.

Thanks again for taking the time to share your ideas with us.
Please keep them coming!

Mads Torgersen, C# Language PM.


With 2 to 3 years between releases, it seems this will not happen***, if ever,
before vs2012(2013?) RTM's.

*** Unless the version of c# can be decoupled from the release of the next
vs IDE to follow vs2010.

Gerry

[Daniel Cazzulino]

yeah, but continuing to vote keeps the issue in their radar, I think...

/kzu

--
Daniel Cazzulino | Developer Lead | XML MVP | Clarius Consulting | +1 425.329.3471

--
Post: moq...@googlegroups.com
Unsubscribe: moqdisc-u...@googlegroups.com

[gerry_lowry (alliston ontario canada (705) 250-0112)]

Interesting comment from Phil Haack*:

"The one minor thing I needed to get used to with Moq
is that I kept trying to pass the mock itself rather than
mock.Object to the method/ctor that needed it.
With Rhino Mocks, when you create the mock,
you get a class of the actual type back, not a wrapper.
However, I see the benefits with having the wrapper in Moq's approach and now like it very much."

g,

* http://haacked.com/archive/2008/03/23/comparing-moq-to-rhino-mocks.aspx

----- Original Message -----
From: Daniel Cazzulino Sent: Friday, November 20, 2009 3:04 PM

yeah, but continuing to vote keeps the issue in their radar, I think...
/kzu
--
Daniel Cazzulino | Developer Lead | XML MVP | Clarius Consulting | +1 425.329.3471

[Daniel Cazzulino]

yup, it gets a bit to get used to, but you end up liking it.

not having mock-related extension methods on everything (as Rhino does) is a big plus IMO.

/kzu

--
Daniel Cazzulino | Developer Lead | XML MVP | Clarius Consulting | +1 425.329.3471