MicrosoftNLayerApp Issue Tracker Rss Feed

Closed Issue: Classes Namespaces bug [4019]

UnaiZorrilla — Thu, 16 May 2013 11:32:23 GMT

The following clasess have a wrong NameSpace. They're missing first namespace part (Microsoft.Samples.NLayerApp…. etc.).

BankAccountServiceTest
SpecificationTests.
SpecificationTests.TEntity (Nested Class)

Check and correct it.

Cesar

Closed Issue: Consider changing Domain Contracts Namespaces - They are a bit mess [4020]

UnaiZorrilla — Thu, 16 May 2013 11:32:23 GMT

We should consider to separate Contracts (Repositories & Specifications) by Entity.
Instead of having a single namespace like:
Microsoft.Samples.NLayerApp.Domain.MainModule.Contracts
And all the contracts classes within it. We could have the following namespaces:

Microsoft.Samples.NLayerApp.Domain.MainModule.Contracts.Customer
Microsoft.Samples.NLayerApp.Domain.MainModule.Contracts.BankAccount

Then, just the contracts for each entity within each..

Cesar.

Commented Issue: Remove OrderLine [6842]

deumber — Thu, 25 Oct 2012 17:15:34 GMT

Hi Team, thanks for share your knowledge with example and book for us.
 
I would like to address the issue of removing a child of an aggregate, such as a use case that would remove a OrderLine of an Order. This does not make much sense for your business logic it is only a good example to respond a situation that is hitting a lot of developer.
 
I found several solutions to the problem but no transparent clean code that maintains a good performance, which makes it seem all the code as a former professor of mine said, touched by god.
 
Here is some link the problem with some solutions:
http://stackoverflow.com/questions/5344477/unable-to-delete-child-entities-from-a-poco-using-unit-of-work-pattern
 
http://weblogs.asp.net/zeeshanhirani/archive/2010/07/23/removing-entity-from-a-related-collection.aspx
 
http://stackoverflow.com/questions/5889886/mvc-3-ef-4-1-dbcontext-deleting-one-to-many-data-object-with-non-nullable-fore
 
http://stackoverflow.com/questions/6125871/ef-4-1-removing-child-object-from-collection-does-not-delete-it-why
 
best regards
Reinier

Comments: ** Comment from web user: deumber **

Here

http://stackoverflow.com/questions/3635071/update-relationships-when-saving-changes-of-ef4-poco-objects/3635326#3635326

and

http://social.msdn.microsoft.com/Forums/en-US/adodotnetentityframework/thread/65eca787-dced-4040-8836-dd5ee437cfca

There is a nice response to this problem

Commented Issue: Remove OrderLine [6842]

deumber — Sat, 20 Oct 2012 18:32:57 GMT

Hi BassemMohsenFarid,

My case is update or delete any item from a collection inside an aggregate. This is not the case in Order and OrderLines but in some use case when you need to update data of an OrderLine and OrderLine it is not an entity because it only life reason is inside a Order, how update OrderLines data?

If you get the Order from the Context and in a perfect OO world you just user RemoveItem from the OrderLine collection and you expect when you said SaveChange the change reflect to the DB.

Maybe this is a Entity Framework lack with all the tracking thing maybe i can do it with self tracking entities or maybe using NHibernate.

Commented Issue: Remove OrderLine [6842]

BassemMohsenFarid — Tue, 18 Sep 2012 12:50:31 GMT

Hi Team, thanks for share your knowledge with example and book for us.

I would like to address the issue of removing a child of an aggregate, such as a use case that would remove a OrderLine of an Order. This does not make much sense for your business logic it is only a good example to respond a situation that is hitting a lot of developer.

I found several solutions to the problem but no transparent clean code that maintains a good performance, which makes it seem all the code as a former professor of mine said, touched by god.

Here is some link the problem with some solutions:
http://stackoverflow.com/questions/5344477/unable-to-delete-child-entities-from-a-poco-using-unit-of-work-pattern

http://weblogs.asp.net/zeeshanhirani/archive/2010/07/23/removing-entity-from-a-related-collection.aspx

http://stackoverflow.com/questions/5889886/mvc-3-ef-4-1-dbcontext-deleting-one-to-many-data-object-with-non-nullable-fore

http://stackoverflow.com/questions/6125871/ef-4-1-removing-child-object-from-collection-does-not-delete-it-why

best regards
Reinier
Comments: ** Comment from web user: BassemMohsenFarid **

You can remove the 'OrderId' property from the 'OrderLine' entity. Generally a mutual reference between domain entities is not a good idea. You will never need to navigate from the OrderLine to the Order, right?

One problem is that the OrderLine record will not be deleted from the database. It will just be disconnected from the Order record. But this is not a big problem in my opinion.

Created Issue: Remove OrderLine [6842]

deumber — Fri, 23 Mar 2012 15:57:12 GMT

Created Issue: Cannot run NLayerAppV2 [6687]

conglee — Fri, 23 Dec 2011 16:27:12 GMT

Hello,
I've just hit this great guidance, but I cannot get the app running.
I see everything is ok with the WCF service at port 2626 and the web at port 1792.
I try to figure the problem with developer tools of IE9 and see that the Silverlight app cannot touch the 2 WCF services, but it received the crossdomain.xml correctly.
Any suggestions for me?
Thanks.

Created Issue: 项目有重复提交SQL至数据库的BUG [6648]

zhuang1125 — Sat, 03 Dec 2011 14:57:00 GMT

项目有重复提交SQL至数据库的BUG
例如：
//get customers
var customers = _customerRepository.GetEnabled(pageIndex, pageCount);

if (customers != null
&&
customers.Any()) //First
{
return _typesAdapter.Adapt<IEnumerable<Customer>, List<CustomerListDTO>>(customers); //Second
}
else
return null;

我做如下修改可以避免：
//get customers
List<Customer> customers = _customerRepository.GetEnabled(pageIndex, pageCount).ToList<Customer>();

if (customers != null
&&
customers.Any())
{
return _typesAdapter.Adapt<IEnumerable<Customer>, List<CustomerListDTO>>(customers);
}
else
return null;

Created Issue: How can I add a property which exists only in Domain ? [6373]

nsdesai — Fri, 12 Aug 2011 09:50:55 GMT

Hello,
I want to add a property in my Business Object which is not available in the Database Table. I want this property in the Domain level Business Objects only not in the Data Tear related BO. Please can anyone tell me how can I achive this? I am using EF4.0 POCO Repository pattern.

Nilkanth Desai

Commented Issue: Redundant string verification in specifications [6313]

santo_pendorcho — Mon, 25 Jul 2011 14:11:21 GMT

In many specification implementations there is used both string.IsNullOrEmpty and string.IsNullOrWhitespace. The IsNullOrWhitespace makes the IsNullOrEmpty redundant because it also returns true for a empty string.
Comments: ** Comment from web user: santo_pendorcho **

http://msdn.microsoft.com/en-us/library/system.string.isnullorempty.aspx
http://msdn.microsoft.com/en-us/library/system.string.isnullorwhitespace.aspx

Commented Issue: IObjectWithChangeTracker [5698]

santo_pendorcho — Mon, 25 Jul 2011 13:43:17 GMT

Hola, estoy leyendo la 1era edicion del libro (Noviembre 2010) y estoy teniendo inconvenientes con la parte de Entity Framework. Primero no me genera los archivos con los mismos nombres que en el libro, es decir el .type.tt no lo genera, lo genera directamente como MainModule.tt y contiene las clases, hasta ahi todo bien. Cuando muevo ese archivo a Domain Entities y ejectuto el Custom Tool, obtengo errores del tipo: "Cannot resolve symbol IObjectWithChangeTracker"

El libro es realmente excelente, los felicito.
Comments: ** Comment from web user: santo_pendorcho **

No pierdas tiempo con la guia de la version 1.0, baja la version 2.0 borrador, y la version alpha del ejemplo, ahi se esta implementando la ultima version de E.F. 4.1
Saludos

Commented Issue: Redundant string verification in specifications [6313]

santo_pendorcho — Mon, 25 Jul 2011 13:32:57 GMT

IsNullOrEmpty:
return value ?? String.Empty;

IsNullOrWhiteSpace:
return String.IsNullOrEmpty(value) || value.Trim().Length == 0;

Created Issue: Redundant string verification in specifications [6313]

eiaro — Thu, 21 Jul 2011 07:42:41 GMT

Commented Issue: Cannot open all projects in solution [6274]

tojo_gd72 — Sun, 17 Jul 2011 15:18:42 GMT

When opening the solution for the first time after getting a fresh copy from SVN, I get an error saying "NLayerAppModeling.modelproj cannot be opened because it's project type is not supported". I'm using VS2010 Pro. Do I need Ultimate to open the solution?

EDIT: I have another machine with VS2010 Premium and that was able to open the proj. Both Pro and Premium can build the app so apparently NLayerAppModeling.modelproj is not required.

Also, I meant to put this thread in Discussions. Can someone move it for me?
Comments: ** Comment from web user: tojo_gd72 **

Only with VS Ultimate can you create modeling projects.
Premium can open the project for viewing, but you can't create new UML diagrams etc.
Pro can't even open the project

Commented Issue: The name of primary key must be "Id" ? [6248]

rclanan — Tue, 12 Jul 2011 15:38:04 GMT

If I use another name like "CountryId" for Country entity , "ID" column will be automatically generated .
Comments: ** Comment from web user: rclanan **

I could be completely wrong on this but I believe the reason you are experiencing this is because the ID field (column) resides on the base Entity class found in the Domain.Seedwork project. If you don't rename that field or remove it and include it in each entity outside of the base class then you will have the ID column automatically generated.

Again though, that's just my assumption as to why you are experiencing that.

Created Issue: Cannot open all projects in solution [6274]

bradirby — Fri, 08 Jul 2011 15:25:25 GMT

Created Issue: The name of primary key must be "Id" ? [6248]

alexpan — Fri, 01 Jul 2011 10:00:22 GMT

If I use another name like "CountryId" for Country entity , "ID" column will be automatically generated .

Created Issue: ViewModels referencing user controls [6237]

Manikrish — Tue, 28 Jun 2011 01:24:39 GMT

In the sample app some of the ViewModels reference user controls. this is not fully complaint with MVVM guidelines where view models should be decoupled from views. Suggest using typeconvertors or something like the EventAggregator in Prism to ensure the guidance is correct.
e.g
Here are some instances:

WPF client (VMMAinWindow)

private void MinimizeWindowExecute()
{
App.Current.MainWindow.WindowState = System.Windows.WindowState.Minimized;
}

private void MaximizeWindowExecute()
{
if (App.Current.MainWindow.WindowState == System.Windows.WindowState.Maximized)
App.Current.MainWindow.WindowState = System.Windows.WindowState.Normal;
else
App.Current.MainWindow.WindowState = System.Windows.WindowState.Maximized;
}
SL client (VMAddCustomer)
private void AddPictureExecute()
{
//Create a file dialog
OpenFileDialog selectPictureDialog = new OpenFileDialog();

//set properties for this dialog ( only once file, title and check that file exist )
selectPictureDialog.Multiselect = false;

if (selectPictureDialog.ShowDialog() == true)
{
string picturePath = selectPictureDialog.File.FullName

Created Issue: ViewModels referencing user controls [6236]

Manikrish — Tue, 28 Jun 2011 01:24:35 GMT

Created Issue: Diferencias entre el comportamiento del objeto MemorySet y EF [6181]

jersiovic — Sat, 04 Jun 2011 18:45:27 GMT

He observado que cuando lanzo una consulta con un join contra la bd si el include lo hago al principio de la consulta este es ignorado. Sin embargo si lo pongo al fina lo realiza correctamente.
Esto hasta cierto punto es normal. El problema es que MemorySet no se comporta igual de manera que cuando la consulta ya lleva el join el siguiente cast devuelve una excepción:

MemorySet<TEntity> fakeQuery = queryable as MemorySet<TEntity>;

Sin embargo si hago el include antes funciona correctamente (al contrario que EF). ¿Se puede hacer algo en el objeto MemorySet para remediar esto?