Skip to main content

New blog engine for the Peter Stegnar programming blog

I have decided to move on with from the custom local blog hosting to the more "modern" variant - cloud.

There are numerous advantages to this. One of the main is availability. Since I have hosted blog in my own infrastructure this was not very reliable service (power and network outages). So now must be much better. If you wonder what was the reliability rate I can tell you, thanks to the great tool Pingdom. It was around 90%-98%. Another main reason is outdated blog. It is '09 release of the DasBlog blog engine. Archaic design, I mess with the blog posting code and so I could only write in pure HTML ... And so consequently I did not write much, actually near to none. I hope I will change this a bit.

You can still reach the old blog: http://blog.archive.stegnar.com/.

Popular posts from this blog

Entity Framework Exception - A referential integrity constraint violation occurred

Entity Framework Exception - A referential integrity constraint violation occurred. When you get this type of the exception it just simply means that you need to match Ids of the related entities. Exception: A referential integrity constraint violation occurred: The property value(s) of 'Image.Id' on one end of a relationship do not match the property value(s) of 'BaseEntity.SomeImageId' on the other end.  A typical mistake that cause this exception is: baseEntity.SomeImageId (type of Image) and Image.Id Does not match. So if you change the new added related entity to the negative Ids ( see the related blog post ), then you also need to modify the parent end of the Id (one end of the relationship as Entity Framework expression goes). So that both "ends" have the same Id value.
Read more

Entity Framework exception - adding new Detached Object to the DbContext

Entity Framework exception - adding new Detached Object to the DbContext? How to? When you see this exception: Exception: Attaching an entity of type 'Image' failed because another entity of the same type already has the same primary key value. This can happen when using the 'Attach' method or setting the state of an entity to 'Unchanged' or 'Modified' if any entities in the graph have conflicting key values. This may be because some entities are new and have not yet received database-generated key values. In this case use the 'Add' method or the 'Added' entity state to track the graph and then set the state of non-new entities to 'Unchanged' or 'Modified' as appropriate. This just mean that you need to properly handle detanched entities Ids. This exception means that two of your newly added entities have the same Id. Typically the value of the Id is 0. So the solution is that you need to manually change Ids. You ...
Read more