Comments for Mehran Nikoo's Notes

Comment on Model-View-* by mnikoo

mnikoo — Mon, 16 May 2011 21:21:40 +0000

When I wrote this post originally I listed MVVMC as a different approach but then removed it because it is the same as MVVM where the reponsibility of the MVVM is further divided between the View Model and the Controller. I have seen people using both approaches (View Model only and View Model + Controller) and there are no rules for when to separate the two so MVVMC can be logically categorised under MVVM.

Comment on Model-View-* by tomb1234

tomb1234 — Tue, 05 Oct 2010 23:19:32 +0000

Now I came here looking for a definition of MVVMC but I’m not convinced yours is correct.

I found myself adding a controller to the MVVM pattern for several reasons:

-Better separation of concerns leading to easier isolation of features therefore improved testability
-On the web it allows the same “page” to contain multiple copies of the same triad, by separating out the controller callbacks (in the form of links) can go to the specified controller rather than being forced to share one

For me it seems that the controller should access the model and the ViewModel. But, like you, I’m finding it difficult to find a proper definition.

Comment on Project and File References Revisited by mnikoo

mnikoo — Wed, 19 May 2010 20:59:45 +0000

Not as far as I know. Deleting a project from the solution in VS2010 still removes all of the references to that project so the behaviour is not changed. This could be a useful feature but it hasn’t been at the top of customer wish list so there are no implementations plans right now.

Comment on Project and File References Revisited by shaggee

shaggee — Wed, 19 May 2010 20:47:07 +0000

Has this been improved at all with VS 2010? It would be nice to have a project reference that a solution would treat as a file reference if the referenced project is not in the solution. i.e. The project reference would also keep a reference to the required file.
VS could even give a warning that the project reference is missing in this solution so it is temporarily switching to a file reference.

Comment on Project and File References Revisited by mnikoo

mnikoo — Mon, 19 Apr 2010 11:01:14 +0000

@ aleko – If the referenced project projects are built already, then the project references shouldn’t be missing. You can build the referenced projects by building a solution that contains those projects. It is common to have one master solution, which includes all of the projects. You build it once after you get latest version and this makes sure VS can find the referenced assemblies.

Comment on PowerTools for Open XML by mnikoo

mnikoo — Sun, 18 Apr 2010 21:49:57 +0000

Yes that’s the one

Comment on VSTS 2010 Beta 1 Available for Download by mnikoo

mnikoo — Fri, 16 Apr 2010 22:06:09 +0000

Original comment by anand on 17/01/2010 23:19:55 entitled 're: VSTS 2010 Beta 1 Available for Download' : i want to check for test manager in 2010

Comment on Project and File References Revisited by mnikoo

mnikoo — Fri, 16 Apr 2010 22:05:53 +0000

Original comment by aleko on 23/03/2010 07:59:32 entitled 're: Project and File References Revisited' : VS 2008 does not compile the solution if project references are missing regardless of whether there are already built referenced dlls or not.

Comment on Project and File References Revisited by mnikoo

mnikoo — Fri, 16 Apr 2010 22:05:50 +0000

Original comment by Mehran Nikoo on 02/03/2009 15:05:14 entitled ‘re: Project and File References Revisited’ : Hi Martin,
It is great to hear from you You are absolutely right. If you have “framework” style projects that are independent of the solution you are working on, then you don’t really need to add them as project references. Those projects will probably have their own solution and they will be developed and versioned independently.

Comment on Project and File References Revisited by mnikoo

mnikoo — Fri, 16 Apr 2010 22:05:47 +0000

Original comment by Martin Pozor on 27/02/2009 08:17:15 entitled 're: Project and File References Revisited' : Hi Mehran. We are going to use this "Multiple Partitioned Solutions" approach (thanks to your advices in my previous job). It looks it will be useful for us. Only one small difference: We will use dll references not only for 3rd party products but also for internal libraries which are not coupled to the actual project (for example library with UI controls which can be also used in other projects). So these internal libraries won't be part of the master build and are absolutely independent (like the 3rd party libraries).