I've installed the WSPBuilder extension for Visual Studio 2010 and I'm looking for a walkthrough of how to create a deployment package for my web-part. Can anyone point me to a good resource? Everything I find seems to be directed towards VS 2008 and it creates the folder structure differently.
Thanks!
The documentation you have found already should be close enough - the hive folder is named "SharePointRoot" instead of "12", but aside from that it's all the same for basic usage.
Developing for SharePoint without having SharePoint on the dev box is going to be fairly painful whatever method you use though. I have a PowerShell script that deploys a WSP on another server so I can use the same development environment for 2007 and 2010 - it works but is a lot slower than the local copy to GAC or hive when making small changes. The error you are getting with VS2008 can probably be fixed by running visual studio as administrator.
Related
I'm looking for some advice. I need to develop some custom workflow activities for a SharePoint 365 online solution. To that extent I do not have a local install of SharePoint 2013. I am using Visual Studio 2012, and have the office developer tools for VS 2012 installed.
When I try to create an empty project for SharePoint 2013, I get the error stating:
SharePoint not installed. The required version of SharePoint
foundation 2013 or SharePoint server 2013 is not installed on this
system. To develop SharePoint solutions or browse SharePoint
connections in server explorer, SharePoint must be installed on the
local system. Make sure that the local server referenced by the
SharePoint project exists
Now, I understand that for SharePoint projects in the past that a local install was required, but with this being online, I do not have that luxury.
Ideally I'd like to identify a way in which I can create an empty project without the need for said local install.
Further to this, I have been able to create an "Apps for SharePoint 2013" project, into which I can create a custom workflow activity. I'm working through some excellent blog posts on how to develop custom activities and it seems to be working file to a point.
What I am now struggling with is that VS2012 is supposed to create an .actions4 file which I can edit to reflect what the workflow activity requires etc. I do not have this file, nor do I understand how I get it.
I would also appreciate information on how I can deploy this custom workflow activity to SharePoint Online so that I can use it in SharePoint designer workflows.
Appreciate there is a lot of asks here, but appreciate any help that people can provide.
Many Thanks,
Grant
Hope this link will help you to create workflows in office 365 . you cannot degug but you can allow visual studio to think that SP is installed on your machine.
https://sharepoint.stackexchange.com/questions/59065/how-visual-studio-checkes-that-sharepoint-has-been-installed-on-my-local-pc
I have SharePoint Foundation 2013 installed in the windows server 2012.
Is it possible to develop SharePoint solution/web parts/Apps using Visual Studio 2012 in my local machine(Windows 7 64Bit) without having SharePoint installed in local machine?
if i need to develop SharePoint solution/web parts/Apps in visual studio 2012, do i need to install visual studio in the Server that contain share point Foundation 2013?
Cant i develop in local machine and deploy it to server?
Can someone help me on this issue?
Thanks.
Try this;
• How to Perform SharePoint Development On A Client Workstation
15 Feb 2011 by Bryant Sombke in Guides, Web, Windows 16 Comments
One of the most difficult restrictions for a SharePoint developer to deal with can be the requirement to do development on a SharePoint server. Personally, I prefer doing my development on my local machine, eliminating the need to establish a remote desktop connection to a different machine in order to write code.
Unfortunately, SharePoint development requires many DLL files which are included with an installation of SharePoint on a server. To make matters worse, SharePoint 2010 requires an x64 server, further complicating the issue. Fortunately, there is an easy workaround that can allow a SharePoint developer to be productive, even while using their laptop on the road without an available internet connection.
Copy the SharePoint DLLs
As I mentioned before, SharePoint development requires DLL files that are included with a SharePoint 2007 or 2010 installation. The first step is to grab these off of a SharePoint server. For SharePoint 2007, they are located in the hive at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI\, and for 2010 at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAP\. Copy the DLL files in this directory from the server, and paste them at the exact same file path on your local machine. Since your PC likely does not have SharePoint installed, you may have to create the directory structure yourself.
SharePoint 2007 DLL Directory
Register the Assemblies to the GAC
Now that you have the DLL files on your workstation, you will be able to include them as references in your Visual Studio projects just as you would with any other DLLs. However, if you want them to auto-register with your project when you use a Visual Studio 2010 SharePoint template or a WSPBuilder template, you must register the DLL files in your local Global Assembly Cache. To do this, open the directory on your workstation that contains the SharePoint DLLs and drag them into the C:\Windows\assembly\ directory. This will register them with the GAC on your workstation, and Visual Studio should successfully find the assemblies when a template is loaded up. Although these assemblies may be 64-bit, this will work fine even though your workstation may be 32-bit.
Global Assembly Cache
If you’ve successfully completed the two steps above, you should be able to write your code and successfully compile your project. Once you generate your WSP file, you can then deploy it like any other WSP.
Please Use Caution
If you do development for both 2007 and 2010, you can do this for both on the same workstation; just be sure to complete both steps for each version. Since the 2007 and 2010 assemblies have different Assembly Versions (12.0.0.0 and 14.0.0.0), you don’t have to worry about conflicts in the GAC. Be sure to use caution, however, because in my experience, Visual Studio tends to grab the SharePoint 2010 version of the DLL even for a SharePoint 2007 project if they’re both registered on your workstation. If this happens, remove the incorrect reference, and add a reference to the correct 2007 DLL from your 12\ISAPI directory.
From http://www.techerator.com/2011/02/how-to-perform-sharepoint-development-on-a-client-workstation/
You can develop SharePoint Apps from anywhere -- this is even more convenient when you're using the SharePoint 2013 development site template to do your testing on.
For farm/sandbox solutions things get more complicated...
If you want to develop webparts or other farm/sandbox solutions you need to have visual studio and sharepoint installed on the same machine (visual studio depends on the sharepoint dlls to build and debug properly). You also need to run Visual Studio as an admin for this scenario (so you'll need to be a local administrator for the machine in question).
It's possible to run SharePoint 2010 on Windows7, but this is not supported by SharePoint 2013 -- you'll have to run Windows Server for the development machine.
You can move your files from a development environment to your production SharePoint farm by building a WSP file for your farm solution on the development machine then sending it to your farm admin who can then deploy it to the production sharepoint environment... For a sandbox solution the site collection admin can add the solution file (WSP) to the site collection 'solution gallery' then active it (for more info on sandbox solution installation see the msdn documentation here: http://msdn.microsoft.com/en-us/library/office/gg615450(v=office.14).aspx)
Hope that summary helps, for more info on setting up development environments see: http://msdn.microsoft.com/en-us/library/office/ee554869(v=office.15).aspx
Yes, you can definately develop SharePoint solutions from your local machine where you dont have SharePoint installed.
For doing this you need to follow some steps -
Go to the server where SharePoint 2013 is installed and follow steps from 1 to 3
Go to Run and type "regedit"
Navigate towards HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office
Right click on 15.0 and click Export. Save the exported file
Now go to your machine where sharepoint is not installed and follow below steps:
Now open Registry on your machine
Import the 15 directory which was exported from SharePoint server
Open Powershell
Run this command
Set-ItemProperty -Path "HKLM:\Software\Microsoft\Shared Tools\web server extensions\15.0\" -Name "Location" -Value "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\"
Now open visual studio 2013 and you will be able to create SharePoint 2013 project without error.
I want to know if it is possible to develop web parts without installing sharepoint?
I choose Visual Web Part then I get sharepoint not installed error.
You can't develop it without SharePoint on same machine.
The answer is "Yes", you can. But if you do that then you loose all features of Visual Studio for development for SharePoint. You will need to create proper visual web part project artifact structure manually which could be tricky. Also you will have to create wsp package manually or using tools like wsp builder. Then you can copy this wsp package to sharepoint server and deploy it.
I am new to SharePoint and I am using SharePoint 2013. I have installed the SharePoint server 2013 on one server and I want to create web parts from vs 2010. But my vs 2010 is present on different pc and I am getting the below error.
"A SharePoint server is not installed on this computer” in SharePoint 2013".
I have search on net and found some links. I have used the below link to create the web parts.
Link : http://sharepointcustomization.blogspot.in/2012/10/sharepoint-server-is-not-installed-on.html
So I have done the below chagnes to create a web parts.
I have Copy the whole registry keys to my local pc.
Copy the SharePoint dlls at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI from sharepoint server to local machine.
Copy the necessary sharepoint dlls to GAC by using below command.
c:\Program Files\Microsoft Visual Studio 10.0\VC> gacutil.exe -i "c:\Microsoft.SharePoint.dll"
I have restared my pc and geting the same error as "A SharePoint server is not installed on this computer” in sharepoint 2013".
Can any one help me to resolve this problem.
As far as I know you need Visual Studio 2013 to develop SharePoint 2013 application.
Just one thing, if you are creating sharepoint apps you don't need to go through all steps in your link. Just go to this page and download the napa development tools.
And as the other people said, it is NOT a good idea to develop farm solutions on a server where SharePoint is not installed. You are practically begging for trouble and to be honest, it's really hard to produce anything without debugging possibilited.
Just my five cents.
In my experience it is still better to have SharePoint installed locally for development purposes. I highly encourage you to just virtualize your development environment as cod
AFAIK you need to have the visual studio together with the SharePoint Server installed (in your case, VS2010 must be installed in you server). It seems that you have the same problem as this guy, check out Eric Herlitz answer SharePoint 2010 Development with Visual Studio as the other answer only pertains you to installing either sharepoint in your pc or vs2010 in your sharepoint server. You would only be limited to using Rest API and/or ClientContext API or external connectors.
I have recently upgraded my SharePoint 2010 solution to SharePoint 2013 and in the same process upgraded the solution as well to Visual-Studio 2012.
One of the things I have observed is that I don't have the "deploy" option at each SharePoint project level. On digging a bit further I have noticed that the "deloy" option is available to all projects under solution but not for projects under any folder.
e.g. I have attached the image showing the solution structure containing two projects. As seen the "deploy" option is not available for the project under the folder.
Is this a bug or is there something setting in VS to make this work?
-Sharath
It's the very definition of a bug.
See also http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/199f8fdb-afbd-4c40-b28c-beba6fc41fbf/
Update 2 - and still no fix.
Edit: Fun fact. If you select two or more projects - the deploy option re-appears -.-