Our intranet (apache/php) is currently talking to our Exchange 2003 server via webdav. Our company was looking at upgrading from Exchange 2007 a while back, we even had the test server up and running and there was some effort made to port our webdav functionality to use the new EWS. The project was shelved for a while, but we are now looking at upgrading to 2010. Are there any big differences between the two EWSs? (I haven't been able to track down any articles about 2007 2010 EWS code migration.)
Answering to close this up. No modifications to EWS code were needed when migrating between servers.
Related
I purchased an ITHit .NET SERVER licence in May 2008, for an ASP.net application, c#, that works fine when on the client side is MS Office 2003.
The documents are stored in a MS Sql Server database and I use a custom IHttpHandler to process the documents.
Since the organisation started to increase, new licences of MS Office (2007/2010/2013) were purchased and instaled on client side.
Although I followed the instruction stated on the page: http://www.webdavsystem.com/server/documentation/ms_office_read_only/, couldn`t make it work with MS Office 2007 and further (still opens documents as read-only).
In order to provide for my client, would it work by aquiring a new licence/upgrade the existing one, or is it possible to fix this issue with the existing licenced version of ITHit WebDAV Server Engine for .NET?
Please keep in mind that I need a solution that still have to deal with a mixed environment of MS Office, meaning there still will be used instances of 2003, 2007, 2010 and 2013, and even 2016, for the next 3 years.
I am working on the project where we are migrating from SQL Server 2000 to 2005 and also migrating from 2005 to 2012 or 2014. There are 30 databases that supports more than 45 applications. Some of the applications are Windows desktop and some are web based application.
My question is if I change the server than there will be problem in connection string and I have to change the connection string of all the applications in the code, right?
Is there any way that I do not have to change the connection string in the code of all the application?
What do you prefer?
PS: Most of the application are in C#, ASP.net
if done correctly, the connection properties should be exposed via a file or application setting. Updating the file/setting to point to the new SQL Server should be quite trivial, although it will require quite a bit of coordination, especially for the client apps. Web apps should be simple, IMO. I am willing to bet you will hit more issues related to permissions and such, because in my experience, it's the logins/pwds/roles that aren't migrated properly.
I have asked our IT to do it but couldn't do it right away. Is this a difficult procedure for MOSS 2007 admins? I'm curious about the step by step process to accomplish adding other database connections.
I think I may have found a solution to connect to database using SPD 2007, the secret was to avoid what they call “double hop” between machines on a network. This is resolved by using MOSS 2007 SSO (Single Sign-On) whereby it results to just “one hop” during database calls to web servers.
The SSO needs to be mapped by configuring the Application Definition which only server administrators can create and modify, using the browser-based Central Admin UI.
Can you help set this up using Central Admin UI please? Step by step process is described on this link http://blogs.msdn.com/b/sharepointdesigner/archive/2007/08/27/an-introduction-to-single-sign-on-sso-with-data-views.aspx?PageIndex=2#comments
With Single Sign-On, you can connect to an external database, even if it doesn't reside on the same server as your SharePoint site.
http://office.microsoft.com/en-us/sharepoint-designer-help/add-a-database-as-a-data-source-HA010100908.aspx#BM4
I am new to SharePoint Server 2007 Web Part, and I am using SharePoint Server 2007 on Windows Server 2008. I program using VSTS 2008 + C# + .Net 3.5.
I want to create a simple web part which could display page creation time and modified time (display such time information at the bottom of a web page).
Any reference code samples or tutorials -- anything helpful for a newbie of SharePoint 2007 Web Part or this specific time tracking issue is helpful.
thanks in advance,
George
Developing for SharePoint is a big leap - for example, the official scenario is doing your development directly on a server. So most SP devs end up building a virtual machine for their development.
Creating an SP dev environment.
Creating a custom web part for SP2007.
Personally, I use the VSeWSS add-in (version 1.3, March CTP) for developing sharepoint "solutions" (really, cab files that wrap up functionality) that contain "features." Many devs prefer other tools, such as STSDEV or WSPBuilder.
Once you get that far creating the web part you need should be simple.
We have Exchange integration into our CRM (diaries and email); we have done this through CRL functions in our SQL 2008 server which handle all the authentication and communication with Exchange 2007 web services. The CLR then presents the functions to developers in SQL Server as regular functions and stored procedures which makes coding wit them simple. We are handling our synching through SSIS to sync the data up.
Unfortunately i cant just install exchange 2003 onto our network Our sales team are in the middle of negotiating a sale that will require me to back migrate the code to work on Exchange 2003. When i am looking to back-port the interface what are the main functional differences between the exchange 2003 and exchange 2007 web services?
What are any potential pitfalls i might face ?
Thanks :)
There are no EWS for Exchange 2003.
EWS were introduced in Exchange 2007.
Exchange Web Services - What You Didn't Know – Exchange Team Blog … (2009-03-25)