I have signed up for office 365
which provides sharepoint site,
I am able to edit the html content of the site.(using Microsoft SharePoint Designer 2010 and Web interface)
Question 1. How to edit the C#/VB code of the site web pages?
Question 2. I have created some asp.net pages and want to upload them to my site, How to use FTP for sharepoint site?
Question 3. How to access data from database for a sharepoint site?
P.S: I have vs2010 but cant open the office365 site ,
also I tried Microsoft SharePoint Designer 2010 but it doesn't display the code behind C#/VB.NET code
You can't just go poking around and do what you want on Office 365 - they don't let you because you can cause problems for the rest of the server.
Instead you have to look at implementing your features as "Sandbox Solutions".
The idea of the sandbox in hosted SharePoint installations is that it restricts the amount of damage (intentional or otherwise) you can do the the rest of the site if your web part does something silly.
MSDN - Sandboxed Solutions
Warning - from your question (e.g. upload .asxp to SharePoint via FTP) its clear that you are very new to SharePoint so you're going to be on a very steep learning curve - start with learning the basics about SharePoint before going onto 365 and sandbox solutions.
Just developed an application for the client. What we did was to setup a virtual environment using VMWare workstation software where we used the following setup:
Microsoft windows 2008 64 bit
VS 2010
Share Point 2010
now while developing applications if you want to setup visual web parts usual visual web parts would not work you have to get an extension for visual web parts(Sandboxed). This extension, not included in visual studio, would give you an option of creating a sandboxed visual web part. You can download it form here:
http://visualstudiogallery.msdn.microsoft.com/8e602a8c-6714-4549-9e95-f3700344b0d9/
After you create the webpart use the wsp to setup solution on office 365 platform.
You will have to use a local site to develop and check if the functionality is working.
The database that can be used in office 365 is the SharePoint lists nothing else.
Cory Roth has quite a good overview of the steps required to package your code and deploy it to the Office365 SharePoint sandbox:
Office 365 How to: Build and Deploy a Web Part with SharePoint Online
In general, you'll need to be deploying packaged features that you can install and run - SharePoint's not really that keen on random editing of .cs/.vb files - you'll need to supply it with a compiled DLL.
Edit to add
Sadly yes, you need a 64bit operating system to "run" SharePoint 2010 on Windows7:
Setting Up the Development Environment for SharePoint 2010 on Windows Vista, Windows 7, and Windows Server 2008
And yes, for development and testing purposes you should indeed have a Local copy of SharePoint - especially when deploying to a Sandbox environment where not everything is available.
yes you need a local SharePoint installation to start developing for SharePoint / SharePoint Online. To dig into SharePoint development you could use the 14 day free trail from cloudshare.com. Cloudshare is offering cloud hosted SharePoint developer machines.
SharePoint Online development is very similar to SharePoint OnPremise development. There are some limitations. You should have a look at Sandboxed Solutions in SharePoint 2010. There are several video trainings available on channel9 targeting SharePoint development.
Paul Stubbs also published the Easy SharePoint Setup script http://blogs.msdn.com/b/pstubbs/archive/2010/10/27/sharepoint-2010-easy-setup-script.aspx.
Use this script to automatically setup you SharePoint development box. There is also this great MSDN article describing the setup process and the requirements http://msdn.microsoft.com/en-us/library/ee554869.aspx.
Thorsten
Related
I'm trying to deploy a simple web part to SharePoint 2013 using Visual Studio 2013 and I am getting the following error:
Error occurred in deployment step 'Activate Features': Feature with Id
'....' is not installed in this farm, and cannot be added to this
scope.
Spent a long time trying to find a solution to this. Several blogs and forums talking about it and giving different solutions (none worked for me).
Feature scope is set to site, and solution is not set to sandbox.
Deployment works if I select the option to skip activation. But then when I go to Site settings and look at features I cannot find it. (I looked at both Site Features and Site Collection Features).
I have tried to change permissions in several different places. I made the user the site owner as well as the site collection administrator (tried both primary and secondary), but it didn't seem to make a difference.
I'm new to the whole complicated world of SharePoint, so bare with my lack of exact terms. Before going for this farm solution I tried with sandbox and everything worked fine: I was able to debug and deploy.
I know there's a way to deploy using PowerShell but I don't think that's the ideal solution here.
Any suggestions? Thanks!
if you skip activation you should deploy feature by script.
Steps to deploy a webpart
1 - in the project settings go sharepoint and select "No Activation" for "Active Deployment Configuration"
2 - Deploy the project
3 - Run the code below in management shell (Run as administrator the management shell)
install-spfeature "yourProjectName_FeatureName" /*exp: TEST.Webparts_Feature1*/
4 - Deactivate - activate fature in "Site Collection Features"
Hi We have a web based SharePoint 2010 webapp and our client is upgrading their os with Office 2013. Would there be any compatibility issues when uploading and downloading document from Document library of our SharePoint app.
Do you guys foresee any concerns of any compatibility issues. Probably any new formats with aren't available with SharePoint 2010.
I can't imagine there being any problems, Office2013 does not use a different file format, it's just a new interface.
There are some new integration features between Office2013 and SharePoint2013 which your client will not have access to in SharePoint 2010, but they certainly won't impact on the functionality of your existing SharePoint Apps, and I can't imagine anyone even noticing that they don't have access to a new feature that they never had before!
I know that I in the past was able to find the code used for the visual studio part of the azure sdk.
Need to see how visual studio selects certificate and generate remote access passwords when creating cloud services. But I have had no luck searching around in https://github.com/WindowsAzure for it
Need the c# code that selects a certificate and uploads it to azure for the deployment.
Not sure where the actual SDK source is, but I've posted this solution on SO and my blog for Securing Azure ServiceConfiguration values for Enterprise Deployment. Writing the code to encrypt/decrypt is trivial and full examples are provided. Adding the certificate to a deployment is also easy - just add it to to role settings. Depending on which SDK you are using, you may have to run with elevated privledges.
I Have a solution that containts 4 layers (3 Class Libraries and 1 Web Application). I Need to deploy this solution to my shared hosting account. I've read a little about deployment and I hope I could perform a 'Precompiled Deployment' because as far as I know, It gives a better experience for the first time users as it's already compliled.
I don't see the "Publish Application" or whatever under the 'Build' menu, I setuped Microsoft Website Copy Tool. and I have on my shared account the Deployment Tool. I'm using Visual Studio 2010 Pro.
..Any one can help with details to deploy my first website on the internet !? :)
Right click on your web application the solution explorer. Select 'publish' from there or is it disabled?
I need to be able to create basic MS Project items (tasks, projects, resources, etc.) programmatically from my app to my Project Server 2003 install, and haven't found any good examples. Can anyone point me to some good references or have some sample code of connecting to the server and creating these items?
Developing against Project Server 2003 isn't the friendliest experience around, but I have worked a little bit with the PDS (Project Data Services) which is SOAP based
http://msdn.microsoft.com/en-us/library/aa204408(office.11).aspx
It contains .NET samples there
As far as I know, the only programatic access to PS 2003 is through PWS.
I don't know if it would work, but you could try writing a managed extension for Microsoft Project 2003 (The client application) .There is a managed API for MS Project 2003, and you might be able to leverage that to communicate with the server, get a project and update it all in code.
Good luck!