I wanted to try team foundation server, so I searched it on microsoft, found tfs express 2012, and installed it on a notebook with windows 7 home premium.
The installation was successfull, but when I followed the procedure for creating a new project it asked for a login. I didn't knew what user/pass to use, I tried some, didn't work.
I tried to create a new user (both in windows and in tfs); didn't work.
Apparently all boils down to a feature of IIS, "Windows Authentication", which this windows can't have.
So the question is:
did really microsoft made a piece of... software that can't work?
is there another way to authenticate?
I tried to login in tfs and the DefaultCollection with chrome and ie, no success either.
It sounds like Windows 7 Home, is not suitable for running TFS Express as it depends on the features of IIS that don't work in Home edition. There is nothing explicit in the System Requirements about editions, but if you are saying the Windows Authentication feature of IIS doesn't work on Home edition, then I guess it won't work. TFS on-premise only uses IIS Windows Authentication.
If you want to try out TFS, why not try Visual Studio Online, this is TFS 2013 plus some updates that will appear in the on-premise version later. It can be used for Free for a team of up to 5 developers.
Related
I have a centralized Microsoft Sharepoint Server and SQL Server on Windows Server 2008 intalled. I am new to sharepoint. In my local machine i have installed Visual Studio 2010 Ultimate Trial version. When i goto create new share point project in the visual studio, I am getting an error message saying,
"A sharepoint server is not installed on this computer. A sharepoint server must be installed to work with sharepoint projects"
Is it possible to develop the sharepoint application like this? if yes. can you please let me know what i can do?
--
Regards
You should install SharePoint 2010 on that machine. Either install it on Windows 7-8 or Windows Server 2008-R2
http://msdn.microsoft.com/en-us/library/ee554869.aspx
Check this Installing Microsoft SharePoint Server 2010 on Windows 7 x64 along this follow msdn.
you should have 64-bit version of Windows 7. then follow the step
mentioned in the above link. Install the additional prerequisites carefully else the installation will cause some error.
Here is the scenario: My dev environment is a Windows 2003 virtual server, MOSS2007, VS 2008, SQL2005, .net Framework 3.5, Ajax 2.0.
We're in the process of upgrading user workstations to Win 7. So I decided to install VS 2010 alongside VS2008.
When I tried to open an existing VS2008 project that has custom web parts for the MOSS, it went through the upgrade wizard but at the end it failed but I did not note what the error was. Instead, I decided to recreate the project but when adding a new sharepoint webpart to my solution I received an error stating that SharePoint must be forst installed on the server. Well lah-di-dah, it is installed!!! So now what?
Ended up uninstalling VS2010, but that is not the point. Does VS2010 requires SharePoint 2010 to work, really? Can anyone elaborate on this. Thanks.
Eric
You tried to open up a Sharepoint solution on your new Windows 7 workstation? I doubt you've got Sharepoint installed on that workstation, so the error message might be correct when it's saying Sharepoint isn't installed.
But, you can use VS2010 to do some Sharepoint 2007 development, as written here: http://social.msdn.microsoft.com/Forums/en/sharepointdevelopment/thread/bbced82a-a0e2-4a50-836a-3deb96c02de8
You still might want to have WSPBuilder installed though, even though VS2010 works pretty slick out of the box.
I've reinstalled both versions of VS and that soleved the problem. (not the most efficient method, however).
I've been using the trial edition of Visual Studio 2008 Team System to develop projects and work with my client's Team Foundation Server. I am using the Team Explorer integration / source control plugin.
My trial is expiring and I'm having trouble finding information on what exactly I need to purchase. I don't need to actually run a TFS server myself, but I do need the ability to connect to my clients and get/put files, and the integration with Team Explorer in VS is really nice, hence I'd rather not have to use an external 3rd party tool.
Do I need Team System to accomplish this or does Visual Studio 2008 Professional have the same TFS Plugin, and if so does it work the same?
I can't believe I'm having such a hard time finding the differences between the versions... if anyone has a good resource that'd be nice before I shell out $3,000 on something I don't need. I develop mainly ASP.NET Solutions if that matters. Thanks!
Visual Studio 2008 Product Comparison Guide
I don't need to actually run a TFS server myself, but I do need the ability to connect to my clients
Whoever is running TFS should procure CALs (Client Access License) so that any client that works with this server is covered. I believe you buy them separately per client machine (somewhat around 400$ each). Also VS Team System editions have one or two CALs included. That may be or may not be worth it for you.
And yes, you can access TFS from VS 2008 Pro, just need to install the integration plugin.
I don't know if that is possible at all for you, but if you can, I would wait for Visual Studio 2010 (to be released in march 2010). Not only is it a better product than VS2008 but also they have simplified the versioning/licensing part, also Team Foundation Server 2010 Basic may be suitable for your source control needs.
If you want to take a look, you can download the beta versions of VS2010 and TFS2010.
I'm currently in the process of investigating TFS 2010, as it's been agreed that we'll be getting VS2010 Professional when it's released and it comes with TFS Basic (we're currently stuck with VSS, and were considering moving to SubVersion prior to the TFS Basic announcement).
I've downloaded an installed the Beta 2 of TFS 2010 and installed it using the Basic installation, which I'm led to believe is what the actual TFS Basic would be equivalent to. I configure it all, install the Team Explorer into Beta 2 of VS2010, and begin nosing around. I see lots of interesting looking options, and turn on one for my test project that says Check-in Policy - Code Analysis. I then try checking in something to that project, and a little dialog pops up saying
Evaluation of Code Analysis Policy
requires Visual Studio 2010 Premium
Beta 2 or Visual Studio 2010 Ultimate
Beta 2 to be installed
However, I can't find any reference to this or other limitations online anywhere. The MS VS 2010 feature comparison page gives all three versions 4 stars for TFS product features, and the pages I've read on the limitations of TFS Basic only say it lacks Sharepoint and Reporting capabilities.
Am I missing something here? Is there an article somewhere on the limitations, or perhaps some confusion between a product TFS Basic and a basic install of the full version?
Sorry this is so confusing. Few things first of all.
VS 2010 Professional with MSDN comes with TFS. Not just TFS "Basic" but a full server license to TFS and a CAL (client access license) to access it. When you install TFS you can then pick what installation option you require. You can go for "Basic" which configures all the pre-requisites for you (such as IIS, SQL Express etc). Or you can go for Advanced if you want the more traditional TFS installation where you can install IIS, MOSS, full SQL Server with reporting services etc first and then install a full TFS that is integrated with these products. You can think of "TFS Basic" - as "Easy TFS". It's the same TFS, just easy to install (including on non server operating systems such as Windows 7 etc). You can move your project collection created on a basic installation of TFS to a full blown TFS installation in the future if you find you outgrow the basic installation.
Check-in policies are bits of client side code that run every time you perform a check in. The particular one that you selected actually runs some features in visual studio to do with code analysis. The problem you are running into is that those features are only available with the premium editions of Visual Studio and is not included in Professional. The feature on the TFS (server) side is just being able to run check-in policies. The feature on the client side is what the check-in policy is calling. Confusing I know.
My tip with check-in polcies would be to not enable them at first and switch them on gradually (see http://www.woodwardweb.com/vsts/policy_override.html for my rationale behind this).
Hope that helps.
Martin.
Does anyone know how you can install/run the TFS Team Explorer in stand alone mode when Visual Studio 2008 is installed on the same machine?
Additional Information: I should have been a little more clear in my question. I'm trying to access the Work Items.
The TFS Team Explorer will always integrate with a version of Visual Studio (apart from Express) if it is installed and there is no way of running it stand-alone.
If you install the TFS 2008 Power Tools, then you can have it so that you get Windows Explorer integration for TFS which many people enjoy. You might also want to look at Team System Web Access to provide a mechanism for accessing TFS from just a web browser (but obviously doesn't include full version control capabilities)
Finally, the company I work for has a completely standalone TFS client called Teamprise Explorer that is implemented in Java, however this is a commercial product.
Hope that helps,
Martin.
The answer is that there really isn't a standalone version. When you install VS Team Explorer on a machine without Visual Studio, the installer will install a Visual Studio shell. Then, when you run Team Explorer in standalone mode, you are actually running a Visual Studio shell.
Martin had a good point about Team System Web Access, which probably would do the job nicely. Plus it has the added benefit that it allows non Visual Studio users access to work items. But, it was decided that it was too much trouble to get permission to install it here (working for the US Army can have its issues).
My solution for now is to run another instance of Visual Studio and access the Team Explorer tools from there.