Wondered why my google analytics data was going up when there was not any content update in last 6 month or so.The secret was comment spam ;-(
Massive comments’ spam has been cleaned up. New version of BlogEngine has some better spam fighting features.
Blogengine 1.6.1 has some new admin features as well that allow more or less bulk comment deletes.
An upgrade from version 1.5 of BlogEngine to 1.6.1 was pretty easy since I did not have too many customizations. Left “themes” and “app_data” folders unchanged > deleted everything else > uploaded new files from version 1.6.1 without overriding before mentioned folders.
I stumble upon this
post the other day.
This led me to wonderful online tool
http://www.websequencediagrams.com/ .
The SD/MSC Generator is an easy alternative to using mouse-centric tools like Microsoft Visio.
It has nice Domain Specific Language and API for creating quick sequence diagrams.
I would prefer this approach for creating any UML diagram anytime over any mouse-centric diagramming tool. Any UML diagram drawn will be rarely revisited later and adjusted/updated to the reality of the live code base. Usually when some process is better can be presented visually you want to have it done as quickly as possible while the idea is still fresh in you head. With traditional tools you would probably spend 70-85% of your time resizing horizontal and vertical lines, boxes, searching for the right shape and stencils, trying to remember to save the document in the correct format and with all this “noise” you loose concentration and spend 3-4 hours on simple diagram that would take 30 minutes to one hours with the tool like SD/MSC Generator. It is so much easier to learn Domain Specific Language for this tool than count pixels on the Visio grid.
And here is the best part of tool like this: you can store text/instruction for your diagram as regular text file in your favorite version control system rather then binary file.
Disclaimer: I am in no way affiliated with this product.
I just found another tool or technique that makes more sense, to me, and makes software project more Agile and less bureaucratic.
//SINGLETON - C#
using NUnit.Framework;
[TestFixture()]
public class SingletonTest
{
[Test()]
public void ObjectsAreTheSameTest()
{
DeploymentInfo firstDeployment = Singleton<DeploymentInfo>.UniqueInstance;
DeploymentInfo secondDeployment = Singleton<DeploymentInfo>.UniqueInstance;
Assert.AreSame(firstDeployment, secondDeployment);
}
}
//Singleton Pattern
//Generic Version
public class Singleton<T> where T : class, new()
{
private Singleton()
{
}
private class SingletonCreator
{
static SingletonCreator()
{
}
// Private object instantiated with private constructor
static internal readonly T instance = new T();
}
public static T UniqueInstance {
get { return SingletonCreator.instance; }
}
}
'SINGLETON - VB.NET
Imports NUnit.Framework
<TestFixture()> _
Public Class SingletonTest
<Test()> _
Public Sub ObjectsAreTheSameTest()
Dim firstDeployment As DeploymentInfo = Singleton(Of DeploymentInfo).UniqueInstance
Dim secondDeployment As DeploymentInfo = Singleton(Of DeploymentInfo).UniqueInstance
Assert.AreSame(firstDeployment, secondDeployment)
End Sub
End Class
'Singleton Pattern
'Generic Version
Public Class Singleton(Of T As {Class, New})
Private Sub New()
End Sub
Private Class SingletonCreator
Shared Sub New()
End Sub
' Private object instantiated with private constructor
Friend Shared ReadOnly instance As New T()
End Class
Public Shared ReadOnly Property UniqueInstance() As T
Get
Return SingletonCreator.instance
End Get
End Property
End Class
