How can I disable all of my features in SharePoint using the WSPBuilder tool without doing it one by one manually?
You cannot do that with WSPBuilder.
You can use SharePoint Manager to easily disable Site Features in an Explorer-like view, or write a PowerShell or .NET code to acomplish that.
Related
Is TFS 2015 is compatible with SharePoint 2016? Google search shows it is not compatible but didn't find any updated reference.
It's probably not compatible. The TFS integration with sharepoint is, at this point, more or less abandoned in favor of more flexible built-in dashboards, graphing, and reporting capabilities. You can still use Sharepoint for document management without having it explicitly integrated with an instance of TFS. I always recommend examining what you're using Sharepoint for in the context of TFS. I think you'll find that it's unnecessary to have it integrated.
I have used SharePoint's export/import tool in SharePoint 2007... Wasn't too thrilled with it. I am now having to do the same thing in SharePoint 2010. First off, just as a refresher, what all is migrated when using the export/import utility? And, is the export/import the same in SP 2010 as it was in SP 2007? If any issues have been seen with the SP2010 export/import utility, I would like to hear that as well. Thanks in advance.
From my experience Powershell export/import works much better in SharePoint 2010 than the stsadm versions did in 2007. However, I also know that export/import improved considerably over the full lifetime of the 2007 product and continued to receive updates up to at least SP2, maybe further with hotfixes and cummulative updates.
I haven't found much missing after experimenting with the flags when exporting then importing a list or a library. I haven't tried the moving sites as much, but I know it is improved over the release version of SharePoint 2007.
I am new to sharepoint and installshield. My responsiblity is to build and deploy the sharepoint solution as a package using istallsheild. Previously I was using solution package wsp and content database restoration. But now the client wants to deliver the total solution i.e. dlls, ascx files, xml files, servce files(.cs), feature files using installsjield from development server to another (test and/or client) server.
Can any body help me on this: how to do the sharepoint deployment using installshield?
thanks in advance.
I presume you are using SharePoint solutions to package dll's, ascx and xml files for deployment to a sharepoint server. These solutions are built using a tool like WSPBuilder.
If not: YOU SHOULD!
If so: Why not use SharePoint Installer? It is an installer wrapper around a .wsp (SharePoint solution) file. It will check for the existence of a sharepoint installation, if the required services are started etc.
For deployment to a test machine: Why would you need the .cs files? If you want to test (debug) code on a test machine, I suggest you use either continuous integration using a tool like CruiseControl.NET, or just install Visual Studio on the test machine (which I presume to be a dev test, not a client test machine) and get the latest version, do a build, then roll out the solution.
And what do you mean with "client" server? is there some windows app that's communicating with sharepoint included in the installer? If so, I suggest separating the SharePoint solution from the actual windows app. They might share DLL's but are not supposed to be in the same installer.
We are using a tool (open source - saf.codeplex.com) to automate the Sharepoint components using MSBuild/Features/STSADM etc. Recently they have upgraded this to use WIX so that we can deploy any SharePoint components.
saf.codeplex.com
It has got an very good documentation and also we got a good support in fixing and implementing the SharePoint automated deployment in our premise.
Thanks
BalamuruganK
i have project in C#, ASP.Net and SharePoint. i want to deploy it usung VS2005 Setup and Deployment tool (As i am not allowed to use any otther software). Can i deploy the Sharepoint part like webparts in VS2005. please tell me what steps i have to take for sharepoint.
All Suggestions are welcome.
Thanks in advance
In short using the VS2005 Setup & Deployment for deploying items to SharePoint is not recommended or not supported.
SharePoint by itself has it well know deployment way called SharePoint Solutions or WSP file. Almost all the items you will want to deployed to SharePoint can be done using WSP(this includes WebPart as well, not only webpart it will allow to add a safe control entry to WebConfig as well). As per your question you are not allowed to use any other tool. To create WSP solution you will not need any extra tool. You can create a WSP file just with notepad (ddf file) & makecab.exe (its avaliable in most of the windows OS).
If you want to make it life simpler try out WSPBuilder and to install the WSP to sharepoint you can use the STSADM command or SharePointInstaller I have been using these tools for past 3 years and they work like charm.
You also have another option of doing it in the Visual Studio just by installing this template VSeWSS version 1.2!
I am new to developing for Office Forms Server / MOSS 2007. I have to choose between designing my web-based forms and writing code for them in Visual Studio Tools for Applications (aka VSTA) or Visual Studio Tools for Office (aka VSTO). VSTA is included free as part of the license for InfoPath 2007; VSTO, also free, requires Visual Studio 2005 / 2008. I have licenses for both of the products and cannot easily decide what the pros and cons of each IDE might be.
This explains it better than I can: http://blogs.msdn.com/andreww/archive/2006/02/21/536179.aspx
Given the fact that the license for VSTA comes with InfoPath, I'd probably run with that.
To add to Bennor's answer I would avoid writing code "behind" InfoPath forms entirely. This is a desperate attempt to make 'dumb XML' as much as possible instead of "smart" XML that is entangled with code. Failing this, my next choice is VSTA because historically these solutions (at least the ones I have written) have a lower security risk and can run on more diverse Office environments.
The last resort is to use VSTO. This is my bias... most of my VSTO investments are in Microsoft Word.