how to debug repository operations? #87
i made some modifications on the model, later i've applyed some migrations to the db. i don't know what is the correct way to regenerate the db from the beginning and resync the migration: i did this:
delete all the migration class
removed the db
i know this is not related with your awesome project, but can you tell me something about this second question as well? thanks a lot
i'm completely fall in love with your project and i'd like to learn a lot about it forgive me for my english.
Thanks. For exception handling, see https://github.com/aspnetboilerplate/as ... t-54001552 You can add this class to handle all exceptions.
Never delete a migration if you applied to database. If you changed model (entities), always add a new migration and update database again.
If you create a migration but not updated db yet, and changed model. In this time, you can delete migration and re-create, then update db.
If you want to create db from zero, then delete db and run update-database command again.
Have a nice day.
thanks a lot, it goes like a rocket :-)
only a question for didactic purpose..
the exception caught from this class(in my case) indicates that:
Source = "Abp.Web.Api" Message = "MSDTC sul server 'OLSAITNB-01' non è disponibile."
the problem is clear: the MSDTC on my machine was Disabled (Distributed Coordinator Transaction Services) ,so i enabled it and evertihing worked
but, what is not clear for me is the source of the exception...
i supposed that, if a problem was generated from something related to the "transaction", the exception should be generated from the "Data" layer (the repository for example, or at least, in the "application layer" where the UnitOfWok is managed, is it right?), . can it be that the source indicated in the "source property" is not so accurate and is referred to the outer layer? or, i'm not understanding how it works?
i aspected that the source of the exception was different
i hope to have been clear enough to express my doubt.
Exceptions are handled in Web API and MVC layers. So, they trigger EventBus events (https://github.com/aspnetboilerplate/as ... ute.cs#L43). This is source of the event, not exception. Also, there is no need for source of the exception since Exception property provides all informations including stack trace.