René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Are exceptions suppressed on purpose upon initialization?","articleBody":"Consider the following initialization code I used for evaluating NEventStore:\n\n```\nWireup\n.Init()\n.UsingSqlPersistence(\"Core NEventStore\")\n.WithDialect(new MsSqlDialect())\n.UsingJsonSerialization()\n.Build();\n```\n\nIt all ran fine in a standalone console applicaiton. However, when I tried to use it in the initialization routines of an ASP.NET web application. The root cause of the error is, of course, missing CREATE TABLE permissions on the IIS user within my database.\n\nIt took me some good four hours to detect this, because the initialization method of the `SqlPersistenceEngine` actively suppresses exceptions. I used a custom `ILog` with breakpoints in each method to jump through all log messages. It seems that the following things happen:\n1. attempting to CREATE TABLE\n2. fails due to insufficient permissions, but the exception is suppressed\n3. transaction gets completed\n4. attempting to CREATE TABLE again\n5. fails due to transaction being already completed\n\nIn the end I was confronted with an exception that had really nothing much to do with the actual root cause of the error.\n","author":{"url":"https://github.com/conradreuter","@type":"Person","name":"conradreuter"},"datePublished":"2016-07-28T11:47:22.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/25/NEventStore.Persistence.SQL/issues/25"}