http://weblogs.asp.net/joshclose/default.aspx.NETifiedenCommunityServer 2007 SP1 (Build: 20510.895)http://weblogs.asp.net/joshclose/archive/2010/12/29/new-net-site.aspxWed, 29 Dec 2010 14:38:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:7670004narshe0http://weblogs.asp.net/joshclose/rsscomments.aspx?PostID=7670004http://weblogs.asp.net/joshclose/archive/2010/12/29/new-net-site.aspx#commentsI recently released a new site. http://www.bid2free.com It's fun to build a site that you own because you get to choose all your favorite technologies and libraries. This is the stack I chose: .NET 4.0 ASP.NET MVC 2 Spark View Engine Ninject Ninject.Web...(<a href="http://weblogs.asp.net/joshclose/archive/2010/12/29/new-net-site.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=7670004" width="1" height="1">http://weblogs.asp.net/joshclose/archive/2008/11/11/asp-net-ajax-addhistorypoint-bug.aspxTue, 11 Nov 2008 18:46:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:6729578narshe13http://weblogs.asp.net/joshclose/rsscomments.aspx?PostID=6729578http://weblogs.asp.net/joshclose/archive/2008/11/11/asp-net-ajax-addhistorypoint-bug.aspx#commentsIn .NET Framework SP1 there was a great feature added that allows history points to be added for Javascript changes. This means, you can use the browswer back/forward buttons with Javascript changes on the page. When released, I went to implement it,...(<a href="http://weblogs.asp.net/joshclose/archive/2008/11/11/asp-net-ajax-addhistorypoint-bug.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=6729578" width="1" height="1">ASP.NETajaxhttp://weblogs.asp.net/joshclose/archive/2008/01/23/appdomain-currentdomain-basedirectory-changed-in-unit-tests-with-visual-studio-2008.aspxWed, 23 Jan 2008 20:57:00 GMTc06e2b9d-981a-45b4-a55f-ab0d8bbfdc1c:5640874narshe3http://weblogs.asp.net/joshclose/rsscomments.aspx?PostID=5640874http://weblogs.asp.net/joshclose/archive/2008/01/23/appdomain-currentdomain-basedirectory-changed-in-unit-tests-with-visual-studio-2008.aspx#commentsRecently I tried converting a solution from Visual Studio 2005 to 2008. Everything seemed to work until I ran all the unit tests. More than 50% of them failed. I found the reason is because AppDomain.CurrentDomain.BaseDirectory changed from 2005 to 2008...(<a href="http://weblogs.asp.net/joshclose/archive/2008/01/23/appdomain-currentdomain-basedirectory-changed-in-unit-tests-with-visual-studio-2008.aspx">read more</a>)<img src="http://weblogs.asp.net/aggbug.aspx?PostID=5640874" width="1" height="1">ASP.NETC#.NET