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!
Related
I need to develop a windows app program. I have Office 2013 in my Machine. And I need to develop the app which supports Office 2013 User machine also. How to do reference dll for it?
I expect that I will develop using Office 2013 and it should supports(the app should work) on Office 2010 also
I have made the app with excel 14.0 reference file. So that if a machine have excel 2010, then the app couldn't open on that
Things go the other way around with Office!
To support all versions of Office back to 2010, you have to develop and maintain your WinForms application with Office 2010, that is the oldest version of Office that you want to support. Whenever you deploy your application on a machine that has Office 2010 or a more recent version, it will work. But it will fail with older versions such as 2007 and 2003.
This design makes sense since one cannot expect that a workook developed with say, Excel 2016, can be run by Excel 2010 without error. The 2016 workbook may use features that did not exist in 2010.
About Microsoft.Office.Interop.Word.
I installed the PIA and Microsoft Office 2010 in my web server, but I can't generate a .doc when I run the application published in my web server. When I run my application in localhost, works fine, and generate the .doc file.
I have to do some configuration in server side to allow the generation of .doc files ?
Remember that Office 2010 was not designed to run inside a web server (e.g., thread safety might not be guaranteed), so you might encounter more difficulties down the line.
Instead, consider using the Open SDK 2.0 from Microsoft, which allows you to manipulate (create, edit) Office 2010 documents, which are simply packaged (zipped) XML files. This technology is much better suited for server use. It also doesn't require you to have a separate Office 2010 license for each web server where you are going to install Office 2010.
You should be using the Open XML SDK for this. The office interops are outdated relics, and should not be used.
Download link:
http://www.microsoft.com/download/en/details.aspx?id=5124
Here's a simple example of how to create a Word document:
public void HelloWorld(string docName)
{
// Create a Wordprocessing document.
using (WordprocessingDocument package = WordprocessingDocument.Create(docName, WordprocessingDocumentType.Document))
{
// Add a new main document part.
package.AddMainDocumentPart();
// Create the Document DOM.
package.MainDocumentPart.Document =
new Document(
new Body(
new Paragraph(
new Run(
new Text("Hello World!")))));
// Save changes to the main document part.
package.MainDocumentPart.Document.Save();
}
}
See this MSDN article for more details:
http://msdn.microsoft.com/en-us/library/dd440953%28v=office.12%29.aspx
Office Interop is NOT supported by MS in "server-like scenarios" (which IIS/ASP.NET is a special kind of)... see http://support.microsoft.com/default.aspx?scid=kb;EN-US;q257757#kb2
Your options include several libtraries (free and commercial) - for example:
MS OpenXML SDK (free)
Aspose.Words (commercial)
Regarding the exception you get:
Since Windows Vista several changes have been introduced to stop any Windows Service (IIS is just some special one) from doing anything "desktop-like" - this is due to security issues... to resolve such a situation you would need to circumvent those security measures implemented by MS - which I absolutely do NOT recommend...
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
I want to develop a report in microsoft sharepoint 2007 which can connect to microsoft project 2007 server , How can I start my work ? Anyone can recommend me some information (book, url, blog etc)
Thanks very much !
Microsoft Project Server 2007 is built on top of SharePoint 2007. When developing for Microsoft Project Server 2007, you have access to all of the APIs provided by SharePoint...all you have to do is use them.
If you're new to developing for SharePoint 2007, I would suggest starting out at the MSDN Library for SharePoint and reading as much as you can:
Microsoft SharePoint Products and Technologies
Just be sure to read the articles/posts for SharePoint 2007 rather than 2010.
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!