Joel misses an important fact in his article... that the same scheme for versioning in.NET is used for the framework itself. So that when the next version of the framework is installed, your application will use the same old version if needed. In theory, no fuss, no muss.
Actually, ASP.NET *will not* validate HTML 4.0 Strict or XHMTL Strict out of the box. The page state stuff MS puts in there will absolutely not validate. You can override the default ASP.NET page rendering processes through code to get it to work, as in this article http://www.liquid-internet.co.uk/content/dynamic/p ages/series1article1.aspx
At my last company we had a development team, half at the client site and half at our office. Since in neither case we had direct lines, we used YM quite effectively to ask quick questions. It also allowed us to pass source code files back and forth, since we did not have an internet based source code control system. It was definitely fast for quick questions that did not need a phone call.
Slashdot Mirror
Umm... close.
- Give the credit when things are going right.
- Take the blame when things are going wrong.
Uhhh.. reads slashdot and comments without reading the article?
Joel misses an important fact in his article... that the same scheme for versioning in .NET is used for the framework itself. So that when the next version of the framework is installed, your application will use the same old version if needed. In theory, no fuss, no muss.
Actually, ASP.NET *will not* validate HTML 4.0 Strict or XHMTL Strict out of the box. The page state stuff MS puts in there will absolutely not validate. You can override the default ASP.NET page rendering processes through code to get it to work, as in this article http://www.liquid-internet.co.uk/content/dynamic/p ages/series1article1.aspx
At my last company we had a development team, half at the client site and half at our office. Since in neither case we had direct lines, we used YM quite effectively to ask quick questions. It also allowed us to pass source code files back and forth, since we did not have an internet based source code control system. It was definitely fast for quick questions that did not need a phone call.