I have problem with connection between 2 webParts in Sharepoint 2007. This option is not visible under my webPart menu.
I have enabled connections in central administration. I have enabled Allow Connection in both webParts I want to connect.
What I need to do to enable it?
It is highly recommended that you use IE 7 or IE 8 for SharePoint 2007. SharePoint 2007 has a known browser compatibility issue in Chrome, Firefox including the problem you are facing. Microsoft resolved this issue in SharePoint 2010/2013 but for SharePoint 2007 you should use IE 8.
Related
I am working with a client who maintains their public facing websites with Sharepoint. They are admittedly out of date and still using Sharepoint 2007 for the most part.
Example Page: http://www.kellerisd.net/Pages/default.aspx
With the recent release of iOS8 their website navigation is now broken in mobile safari and Chrome. I have seen numerous posts regarding the changes to the JS engine for browsers with iOS8 (http://9to5mac.com/2014/06/03/ios-8-webkit-changes-finally-allow-all-apps-to-have-the-same-performance-as-safari/)but have no other means to explain the loss of functionality overnight.
I am working with them to update to SP 2013 which should alleviate the issue but I am looking to repair their site to keep them functional until the migration is possible.
Don't expect SharePoint 2013 to help if they are using Windows Authentication... Windows Authentication is broken in iOS 8 Safari. (Works OK in Chrome though.)
A client runs our Delphi 2007 app on Windows 2008 R2 via Citrix XenApp.
He's been facing an issue where the file open dialog crashes sometimes. He's applied latest updates for windows and Citrix.
I've seen many articles on the net where similar issue occurs for various apps other than Delphi like MS Office apps, VS 2008, Adobe PDF etc.
The client doesn't face this on any other application and thus is blaming our application.
If the our app's "Compatibility Mode" is "Windows XP SP3" then all is fine. Hence, client has raised a question stating if our Delphi app is Windows 2008 R2 certified.
What changes are required if we have to make our Delphi 2007 app certified for Windows 7/2003/2008/2008 R2 ?
We have fixed lots of strange Delphi (2009) app crashes on Windows 2008 R2 64 Bit Terminal Server environment with these additional lines in the DPR:
// make it Terminal Server Aware (app without installer writing to ini files / registry)
{$SetPEOptFlags IMAGE_DLLCHARACTERISTICS_TERMINAL_SERVER_AWARE}
Note: to compile, it requires the Windows unit
The crashes appeared in many unexpected places like open dialogs. With the excellent madExcept tool we found that apps crashed within operating system routines in some Windows DLLs, and disappeared when we added the "terminal server aware" flag.
I am not a Delphi developer but a Google Search for Delphi 2007 System requirement took me to this page http://edn.embarcadero.com/article/36573#requirements
The following Windows platforms are supported:
Microsoft® Windows 2000 Professional or Windows 2000 Server (SP4 or higher and security updates are recommended)
Microsoft Windows XP Professional (SP2)
Microsoft Windows Vista™
Microsoft Windows Server 2003 (SP1)
The latest service packs and security updates are recommended for all platforms
Microsoft Internet Explorer 6.0 SP1 or later
I don't see Windows 2008 here.
Its not uncommon for the following:
It would be up to you to determine and test how your app functions under 2008. Knowing that a number of things as always change with each release of windows let alone server/workstation.
You tell them under what senarios YOU will support your application being run.
If you require your app to be run as compatbility mode with xp sp3, and tell them that, and tell them YOU dont support it outside that configuration. If you wont support it under a virtual environment.. then you tell them that.
Obviously the better answer would be to test it on 2008 R2, and check all your functionality and say you will support it running in a natural state.
hello i have developed a sharepoint 2007 site using MOSS 2007 and wss 3.0. i want to know difference between both. if i deploy this site to another serserver with moss 2007 installed but no wss 3.0, will that site work fine??
thnks in advance
Regards
MOSS 2007 is a product built on top of WSS 3.0.
WSS 3.0 is a set of services provided by Microsoft for free which provides basic capabilities for Document Management.
When you install MOSS 2007 on a server, WSS 3.0 is automatically installed with it.
Check out this link:
http://sharepoint.microsoft.com/blogs/GetThePoint/Lists/Posts/Post.aspx?ID=4
I have created a Visual web part for SP2010 site, What I need is to implement it into MOSS 2007 site.
Does MOSS2007 support visual web part,and how to do this?
I dont see VS 2010 Support Visual WebPart for 2007, but still you can develop a web part using 2010 (not using any of 2010 Feature) and after you completed the development you can package it manually to be deployed to 2007. Yeah its a extra step. Or you can see how smartpart works. Smartpart is nothing but similar concept in 2007 World.
Just installed Sharepoint2007 and VS2010.
Made an empty Sharepoint project, and opened the server tab in VS.
I saw an option to make a Sharepoint connection.
I tried to, but it gave an error, saying that a Sharepoint server is not installed on the machine.
I can surf to Sharepoint's Central Admin, and all is well.
Do I need to have a website running, beside Central Admin, to connect VS, or should VS connect to Sharepoint as I have it (just after an installation)?
John is right, you do need SharePoint 2010.
Check out this msdn thread:
http://social.msdn.microsoft.com/Forums/en/sharepointdevelopmentprerelease/thread/da8de480-778b-4150-bd1b-c66bb75db042