This post originated from an RSS feed registered with .NET Buzz by Sam Gentile. Original Post: Using VSTS/TFS Part 2 Feed Title: Sam Gentile's Blog Feed URL: http://samgentile.com/blog/Rss.aspx Feed Description: .NET and Software Development from an experienced perspective - .NET/CLR, Rotor, Interop, MC+/C++, COM+, ES, Mac OS X, Extreme Programming and More! Latest .NET Buzz Posts Latest .NET Buzz Posts by Sam Gentile Latest Posts From Sam Gentile's Blog

So I mentioned yesterday that I was using VSTS/TFS for real projects I have going.I couldn't leave well enough alone could I? Actually, it was never really installed right as it all worked except for the Project Portal which is the Sharepoint site. Essentially the problem is this: you have virtual directory of 2 different .NET version assigned to the same pool. For ex, say your "Default Web Site" is ASP.NET 1.1 because it is running Sharepoint services. But the "Report" or "ReportServer" virtual directories are in ASP.NET 2.0. You will notice that all these are using the same application pool. So, once you visit http://localhost, ASP.NET 1.1 gets loaded. So, when you create a Team Project and it tries to access the "Report" or "ReportServer" virtual directory, it cannot load because they are in ASP.NET 2.0 but sharing the same pool.

Its really a pain in the rear because I have devoted 48 hours to this (I was up until 5 AM this morning) and I still can't get it to work. Its a big impedence mismatch: Sharepoint wants .NET 1.1 and the rest of TFS/VSTS/Reporting Services wants 2.0 and they don't really match well. I think people are going to have an extremely hard time with all this in production.