I've been looking around TFS 2013 screenshots and I notice how it look like it's implemented over Sharepoint 2013...
So, when i install TFS 2013, do I get a full blown sharepoint (with central admin and everything), just a site collection (a "light" version of it) or none (meaning if, i want a web interface, i have point to my sharepoint and say "use that one")???
PS: Since i'm in a corporate environment i don't have a spare machine to just install it and check it for myself, and other documentation don't make this clear...
TFS has its own web-based interface (TFS Web Access) that isn't based on SharePoint. It also has the ability to integrate with SharePoint which will cause SP-based Project Portals to be created with every Team Project (this is in addition to TFS Web Access).
When you install TFS you can choose to have the TFS Install install/configure SharePoint Foundation, or you can point it to a pre-existing SP Foundation or Enterprise environment.
SharePoint Foundation 2013 can be installed with TFS, if you specify that in the installation.
Reference
SharePoint Products requirements for Team Foundation Server
Related
I'd like to put a table form oracle on my sharepoint 2010 (and soon to be updated 2013) site so that the table can be updated and new rows can be inserted. After googling using BCS seems to be the only option. Is this correct? the Sharepoint designer will not work with Oracle?
Also when I open Visual Studio 2012 Professional and click on new project>>Sharepoint>>Sharepoint 2010 Project I get an error saying
Sharepoint server must be installed to workwith share point projects.
Do I need to install sharepoint server on my machine?
Can anyone provide any documentation on how to do this? what happens when I go to Sharepoint 2013?
Oh yea and I have windows 7. Will sharepoint server work on windows 7?
Thank you!
I'll try to answer all your questions.
Oracle connectivity
BCS supports Oracle but it's not trivial. Sharepoint designer is a tool where you can create External Types (BCS types). But with Sharepoint Designer you are limited to SQL Server, WCF Services and .NET assemblies. There are few workarounds:
Create linked server to oracle in SQL Serve Management Studio and use Sharepoint Designer to create BCSentities
You can create service for fetching oracle data and use Sharepoint designer to create BCS entities
If you just want to display some data from oracle and have developer knowledge. You can use ODAC for .NET and create webparts for displaying data (the simplest solution of all).
For Sharepoint 2010 Development you have to install sharepoint (foundation or server) on copmuter where your VS resides. Sharepoint foundation could be installed on Windows 7 x64. Installation is trivial download sharepoint foundation and run installation file.
For Sharepoint 2013. You can create apps and client apps on remote computer but for farm solutions there is the same rule (but SP 2013 can't be installed on Windows 7).
I want to start my first SharePoint project to build internal and external systems:-
So I am preparing to get the following to set the development environment and to publish live SharePoint applications:-
SharePoint Server 2013 Standard edition. As for now we do no need
the enterprise features such as e-discover, BI, branding, etc.
Windows server 2012 & IIS as the operating system and hosting server respectively.
SQL server 2012 or 2008 for the database
Visual studio professional 2012 to develop web parts and use SharePoint templates.
Team foundation server 2012 to provides versioning control, bug tracing, etc.
So can anyone advice if I am missing any tools or software that are needed to develop and implement live internet & intranet SharePoint applications.
Second question should I use office 365 in my case?
Best Regards
It seems like it's sufficient enough to start developing SharePoint applications. You may need SharePoint Designer 2013. You can also find the best-to-have hardware requirements for SharePoint development environment in my blog post (http://keremozen.com/2012/12/28/hardware-requirements-for-sharepoint-2013-development/).
Office 365 or on-prem installation choice totally depends on your needs.
Office 365 installation provides easy set-up, maintainability, scalebility and security. Your sites will be accessible 24x7. If you want full control on your sites you can prefer on-prem installation.
Regards
We are currently using TFS 2010 and have a Team site of SharePoint 2007. We are currently not using the Team site (we tried out a few things but at the moment its no problem to just remove it).
But we want to use the Team site and thought that we might as well upgrade it to 2010 before starting to use it. Its probably easier to upgrade from a pretty clean install than doing it later.
So.. Is it best to upgrade our site.. or should we maybe install a new SharePoint 2010 on the side and then switch over to that?
Any suggestions on which approach i should take. What is easiest (I don't know if I need to install anything special for Team site than other SharePoint sites)
PS. I am a newbie when it comes to SharePoint but can get some more experienced help if needed.
Easiest way would be to install a new Sharepoint 2010 instance somewhere and point TFS to that. To set it up you need to install SP 2010, then install the SP TFS Extensions off the TFS Install DVD, then fire up TFS Admin console and use it to configure the SP site. More detailed instructions can be found here: http://blog.hinshelwood.com/integrate-sharepoint-2010-with-team-foundation-server-2010/
Once you've got it configured it will auto-create Team Portals for any new Team Projects. If you wish to create Portals for pre-existing Team Projects there is a manual step you need to take that is described here: http://blogs.msdn.com/b/greggboer/archive/2010/02/24/creating-sharepoint-portals-reports-and-upgrading-reports-for-an-existing-team-project.aspx
I know there are so many questions and articles on this topic and I have searched hours and hours on the Internet so far, but I still couldn’t find the right answer for my question. I was assigned the task to investigate the development environment for SharePoint web parts by my company. The money is not an issue but it must be the proper way to do it.
Here is my ideal plan: at developer desktop, install VS2005/2008 (it is already installed), VS2005/2008 Extension for SharePoint and WSPBuilder. It is also installed a Virtual Machine and the VM runs windows server 2003/2008. WSS3.0 and SQL Express 2005/2008 will be also installed on VM.
Developer’s desktop is a web parts development environment. Developers use VS to develop the SharePoint web parts and then run the WSPBuilder, it will deploy the web parts into the SharePoint testing environment on VM. So the VM is just a SharePoint testing environment.
It looks like a good idea, however, it doesn’t work. Why? Because VS extension can't be installed on developer’s desktop as it doesn’t have WSS3.0 installed!
I definitely don’t want to install the VS on the VM, because our developer desktop has installed VS and we don’t need to have 2 VS licences for 1 developer.
Any idea what is the best way to set up the development environment for SharePoint web parts?
Thank you in advance.
You won't be able to develop for SharePoint (WSS 3.0) unless your development environment includes an installation of at least WSS. In general, development is done on a Windows Server 2003 Virtual Machine (Visual Studio is installed directly on this machine). However, SharePoint can be installed on Windows Vista and Windows 7 machines, so your development machine may be able to host SharePoint itself, but it is far easier to do this on a VM.
My SharePoint development VM has the following installed:
Windows Server 2003 R2
SharePoint 2007 (Including SQL 2005)
Visual Studio 2008
Visual Studio Tools for Office
Office Server SDK
Visual Studio Extensions for WSS 1.3
Obviously you can use WSPBuilder instead, but I much prefer VSSWSS 1.3, but that is developer preference.
I believe (should be verified with Microsoft) that the licensing for Visual Studio can be extended to Virtual Machines when used by the same developer (depending on your agreement).
An alternative for you which may or may not work depending on your priorities.
Install Visual Studio 2010 and SharePoint 2010 Foundation to your development server.
Grab a copy of Microsoft.SharePoint.dll from a SharePoint 2007 server.
Use VS2010's tools to develop a web part but manually change the reference to the 2007 dll's (+ also see "Build a SharePoint 2007 Web Part with a Visual Studio 2010 Visual Web Part Project") so you are outputing a 2007 compatible web part.
When you delploy your 2007 web part to your local 2010 server it will just work (as its backwardly compatible)
When you deploy your 2007 web part to your test/qa/production servers it will work too.
Advantages
You're working with latest greatest
version of VS and the sharepoint
tooling so you get one click deploy,
automatic creation of WSP packages
etc. Nothing against WSP Builder etc (they are great) but my moneys on vs2010 sharepoint extensions for the future.
You're ready if/when your
company moves to 2010.
You're developing on a Windows 7 machine, not a 2003/2008 server and or a VM so this has advantages for licensing, speed and ease of use (dual monitor support from VS running on a VM?)
Edit - to deploy web parts to other servers you create a .wsp package and then deploy via STSSADM or another tool (SharePoint solution installer or other admin tools).
I haven't used VSSWSS or WSPBuilder. I've always used STSDEV for SharePoint 2007. And I've always used Windows XP to do it. I don't know if VSSWSS and WSPBuilder act the same, but, as Ryan was saying, I copy whatever SharePoint DLLs I need from a SharePoint 2007 server into a Solution Folder in my Visual Studio solution. I then select Add Reference in my project and browse to the DLL.
In four years, I've never had any problems with this method. The solution packages build just fine and work on any SharePoint server. I lose the option to debug, but I'd rather stay on my machine than go into a VM or Remote Desktop.
I've just tried out TFS 2010 today, along with Project 2010 and VS 2010. Only Later realized that without Sharepoint, TFS is only configured as Basic. This reduces it's functionality as oppose to what I've seen during VS2010 product launch. Sadly I can't find any alternative but to get a trial copy of Sharepoint to see if it serve my purpose. Well, apparently Sharepoint only comes with x64 edition. I'm not formatting any machine to x64 just to give this a try. So, after some reading up, I found that Project Server is actually based on Sharepoint. Now I wonder is whether TFS can be configure to connect to Project Server?
If it's possible, would the setting be much different that Sharepoint's?
And what am I missing from this setup as oppose to Sharepoint's?
Based on Sharepoint != Sharepoint. I think that Project Server is just a subset of Sharepoint functionality. Also, basing Project on Sharepoint allows for some really tight integration into your portal. To answer your question, I don't think you still will get your fully featured TFS without Sharepoint Proper.
FYI - Sharepoint 2007 (or 3.0 or whatever it is) is not x64 only, but will run on x86. TFS 2010 will go full feature on 2007
Sharepoint 2007 Trial
To answer what you are missing:
Reports
Project Portal
TFS Web Access
That's about it. You still get 90% of the features with your current deployment without SharePoint. Tommy is right about MOSS 2007, it comes in 32-bit and will give you all features. Project Server runs on top of SharePoint as a shared service provider. Traditionally MS releases a power toy to integrate TFS with Project Server. They said they would go over this at TechEd, which just happened about a week ago.
Also, I suspect the integration with Project Server 2010 will be better, but then you will have to run SharePoint 2010 :(
In my opinion, TFS has enough to run most projects by itself and you can use the client version of MS Project for critical path anaylsis, etc.
Use Windows Sharepoint Services for Windows 2003 & Windows 2008:
http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb400747.aspx
For Windows Server 2008 sp2 and Windows Server R2, use SharePoint Foundation 2010:
http://www.microsoft.com/downloads/details.aspx?FamilyID=49c79a8a-4612-4e7d-a0b4-3bb429b46595&displaylang=en
Both are free.
I'm not formatting any machine to x64
just to give this a try.
Why not use VMWare Server, Hyper-V, Virtual Box or some other virtualization software to run the pre-made demo/trial/lab VHD's - no formatting, no installation, no setup, more hair.
Link