Comments for Jason Dentler

Comment on Visual Studio 2010 publish / web.config conflict by Simon Lomax

Simon Lomax — Thu, 22 Jul 2010 12:16:51 +0000

@Steve, thanks, that solved the problem.

Comment on Visual Studio 2010 publish / web.config conflict by Steve Evans

Steve Evans — Wed, 21 Jul 2010 21:51:41 +0000

Bah…forget to escape the tags:

Comment on Visual Studio 2010 publish / web.config conflict by Steve Evans

Steve Evans — Wed, 21 Jul 2010 21:50:37 +0000

I came across the same issue, but I figured it out by clicking into the error and looking at the file it had opened up. The give away was the fact that by default it's "Web.config" and when I double clicked the error it opened "web.config" The casing of the "w" seemed odd, but thanks to Visual Studio showing you the full path of the file when you over over the document's tab it helped figure out what was going on. In my case I modified the BeforeBuild target of the project file to include the following:

Comment on Visual Studio 2010 publish / web.config conflict by Jason

Jason — Tue, 20 Jul 2010 23:25:49 +0000

Yep. It’s especially annoying because a person can google around for hours and find nothing but advice about IIS settings.

Comment on Visual Studio 2010 publish / web.config conflict by Simon Lomax

Simon Lomax — Tue, 20 Jul 2010 18:11:09 +0000

Jason, I was getting exactly the same issue last week. I posted this question on StackOverflow but got no replies.

http://stackoverflow.com/questions/3204747/problem-after-publishing-web-application-from-vs-2010

Its a real pain to have to remember to delete the obj folder all the time, which is what I’ve been doing too. Be great if someone knows a fix for this.

Comment on NHibernate Auditing v3 – Poor Man’s Envers by Jason

Jason — Tue, 06 Jul 2010 13:13:37 +0000

That’s a pretty slick solution, but I don’t see the benefit of saving a few tables over the additional application complexity.

Comment on NHibernate Auditing v3 – Poor Man’s Envers by marek

marek — Tue, 06 Jul 2010 07:30:06 +0000

Hi Jason,

well, yes, the approach I’m talking about is maybe not 100% relational, but, I think it could be tuned to be so.
Please see following solution:
http://www.matthidinger.com/archive/2008/05/08/linq-to-sql-audit-trail.aspx
It is using Linq To Sql but we implemented this idea using NHibernate.
Please note in Audit table TableKey and TableName, using polymorphism you could make relation to your entity.

Thanks.

Comment on NHibernate Auditing v3 – Poor Man’s Envers by Jason

Jason — Mon, 05 Jul 2010 10:51:00 +0000

Thanks for the comment Marek.

Would you store your model in a single table with only 3 columns (EntityId, Key, Value). Why not? It’s not relational.

I’ve seen many systems where there is only one Audit table for everything. They tend to be black holes where information goes in and nothing ever escapes.

The point of this exercise is to make this audit data just as available and accessible as the real application data.

Comment on NHibernate Auditing v3 – Poor Man’s Envers by marek

marek — Mon, 05 Jul 2010 08:22:06 +0000

Hi,

interesting…
I don’t know Envers concept, but I’m afraid that the amount of extra tables (additional audit table per entity) can be disadvantage of the solution.
I think there should be a way to do it using two tables.

Comment on NHibernate Auditing v3 – Poor Man’s Envers by Tweets that mention NHibernate Auditing v3 – Poor Man’s Envers « Jason Dentler -- Topsy.com

Sun, 04 Jul 2010 21:00:15 +0000

[...] This post was mentioned on Twitter by José F. Romaniello. José F. Romaniello said: RT @jasondentler: Blogged: NHibernate Auditing v3 – Poor Man's Envers http://bit.ly/c2fAvg Thanks to @jfroma [...]