View Complete Post
I'm working on a SharePoint webpart which i'm targeting for both SharePoint 2007 as well as SharePoint 2010. I want to create a common build to make it work in both SharePoint 2007 and 2010. How should i do that? I'm working on Visual Studio 2010 and my
dev environment has SharePoint 2007 installed.
Also, multiple developers may work in the same solution. Some of them have 2007 installed and some have SP 2010 installed. Will it work?
Do we have some kind of Equivalent of Solution generator 2008 (SharePoint 2007 to generate list definitions and site definitions via SharePoint 2007 UI and use it in our WSP) in SharePoint 2010?
can we run .bat file in cab.ddf file of solution package in sharepoint 2010
bcoz i have created 1 batch fiel which create the hierarchy of folders and move all the images to specific folder so if .bat ll run in my solution package then my problem will solve
help me out
Hi All, I've been scratching my head trying to figure out how to integrate Office Web Apps in to SharePoint 2010 as a hoster. The issue was after following various posts, documents and so on, I could enable the Office Web Apps on the main site collection
but not our organisation as a test tenant. We are running SharePoint 2010 feature pack.
When attempting to add the office feature pack, we would run in to a problem:
Enable-SPFeature : Failed to activate feature 'MobileExcelWebAccess' (id: 'e995e28b-9ba8-4668-9933-cf5c146d7a9f'). To figure out if this was just an issue with the Enterprise Feature
MobileExcelWebAccess, I decided to enable the feature for standard temporarily and discovered a range of services that needed to be added to the feature pack.
So after much thinking about this, we felt that Office Web Apps should be available as a separate feature pack for Foundation, Standard or Enterprise rather than adding to the existing feature packs and migrate the customer, so long as the customer has the
correct SPLA or Volume License.
Based on this, we created 3 new feature packs that supported Office Web Apps. For those who have grappled with this same concept, here are the feature ID's you need to add to t