My company has SharePoint server farm setup and run on internet and local. Now we have to develop some application on it.
How can we do that from VS2010 on PC/Laptop (which does not have SharePoint server installed)?
If we have to remote connect to server and use VS 2010 on server, how can multiple people can work at the same time?
SharePoint development needs ot be done on a system with SharePoint installed (forget about trying to remote, it never works well with SharePoint). You can install SharePoint on your PC/Laptop for development purposes - How to Setup SharePoint Development Environment
You can develop SharePoint applications without SP installed but will be limited to using the REST Api, ClientContext API or an external connector like Camelot .NET Connector for SharePoint from Bendsoft.
Generally SharePoint developers work in a virtual environment with SharePoint foundation installed creating their deployment packages locally.
Here is a good starting point if you want to set a virtual environment up for development. http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx
Related
I have been tasked with setting up a SharePoint 2013 site being a straight MVC developer has me scrambling to figure out how to implement a solution that works for everyone involved.
We have a server with SharePoint on it and visual stuido however RDC only has 2 connections (company will not pay for more connections, tried that route) and we have the potential for 8 developers to be logged in at once.
our local machine setup is windows 8.1 with visual studio 2013 on it.
I read somewhere you can do remote connections to SharePoint but have no clue how to set that up or if it's even possible for use.
if anyone can help point me in a direction that would be great.
If you are strictly developing Apps you can develop remotely and this TechNet covers the step-by-step for it (configure the server and infrastructure for Apps, create a developer site and give your Devs the required permissions).
If you want to develop components that use the server side Object model (Microsoft.SharePoint.dll) you MUST do so from a SharePoint server.
You can try to copy the DLL over to your dev machine, and you can successfully build. With this, though, you will lose many of Visual Studio's integrations and will not be able to deploy or debug from Visual Studio
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
I recently setup a sharepoint server 2013 on our company and have found really good examples how you can override the suitbar with custom links.
Now that I'm trying to implement those examples i get to that point where Visual Studio 2012 and Office development tools is installed.
When i choose to start a new project I select New Project > Templates > Visual C# > Office/SharePoint > SharePoint Solutions > SharePoint 2013 Empty Project hit ok and i get an error that says Sharepoint not installed?
Am I supposed to install VS 2012 and develop om my Sharepoint 2013 server directly?
A very common way to develop SharePoint applications is to run a virtual machine (hyper-v under windows 8 for example) on your development workstation.
You can also dual-boot into a vhd file.
You can also install Windows Server 2012 and use one of the many desktop conversion techniques to use it as your primary operating system on your workstation.
Another often seen technique is to have a virtual machine hosted in the cloud or a datacenter, running both SharePoint Server and Visual Studio. Then connect to that machine using Remote Desktop.
With some trickery, you could have the SharePoint 2010 installer install om a workstation OS. This no longer works on SharePoint 2013. The reason this support was removed is due to the inclusion of Boot from VHD and Hyper-v into Windows 8.
It is my experience that if you just want to build your application and not run or debug it, that just having the assemblies copied over from an actual SharePoint Server will allow you to do that. I haven't found an updated document for SharePoint 2013 yet.
Yes. You have to develop on the sharepoint server directly using Visual Studio as Sharepoint server GAC has the required server object models to work programatically with sharepoint server object model.
You can aslo develop on client machine using Client Object Model or WCF Data Services Framework.
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.