unit testing - Experiences using moq with VB.Net -
I really like the mock joke frame. I have used it on many projects Unfortunately, one of my clients is demanding that we use VBnet. My priority is not, but hey, is the net. Net, right?
I have heard that Mock has some problem with VB, is this true? What is the problem, what happens to the problems? I hope that the language of the net will act as an agnostic nature.
Should I use some other joke outfits for the use of VB?
The main problem of VBnet in relation to shocking motions is that, unlike C #, VB There are no anonymous methods, only lambda bhav (there is no way to declare an unknown action representative).
It severely limits the possibilities. There is also a known issue with the parameters with parameters.
In addition to this, the syntax of language for lambdass is not as pure as C #, readability-wise (no flame, I am VB user and I remember every few # features every day ), And it is partly the attraction for Moq.
I know that something about VB has been done, they tried to design something that mixes with VB syntax.
Comments
Post a Comment