.NETifiedhttp://weblogs.asp.net/joshclose/atom.aspxCommunity Server2008-01-23T14:57:00Zhttp://weblogs.asp.net/joshclose/archive/2010/12/29/new-net-site.aspx2010-12-29T14:38:00Z2010-12-29T14:38:00ZI 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.Mvc NHibernate NHibernate.Linq Fluent NHibernate AutoMapper Dotless (if you haven't tried LESS CSS, you should) Moq Elmah jQuery I feel like I'm in a really nice spot with technologies right now. Yes, they can always get better, but right now I don...(<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">narshehttp://weblogs.asp.net/members/narshe.aspxhttp://weblogs.asp.net/joshclose/archive/2008/11/11/asp-net-ajax-addhistorypoint-bug.aspx2008-11-11T18:46:00Z2008-11-11T18:46:00ZIn .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, and quickly found there is a bug that causes this feature to not work at all in IE. Problem: To use this feature on the client, you enable it by setting EnableHistory="true" on the ScriptManager. What this does is renders "Sys.Application._enableHistoryInScriptManager...(<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">narshehttp://weblogs.asp.net/members/narshe.aspxhttp://weblogs.asp.net/joshclose/archive/2008/01/23/appdomain-currentdomain-basedirectory-changed-in-unit-tests-with-visual-studio-2008.aspx2008-01-23T20:57:00Z2008-01-23T20:57:00ZRecently 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. In 2005 the value returned was the projects test results directory. In 2008, it returns the directory that the executing assembly of the unit test is located. i.e. C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\. The fix for this problem...(<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">narshehttp://weblogs.asp.net/members/narshe.aspx