One of our product will consist of multiple SharePoint solutions. Now we're wondering what would be the best way to provide an easy deployment to our customers? At the moment we deploy each solution by hand, which is OK during development process but not acceptable for our customers.
For your information, we're using VSeWSS 1.3 for development and solution packaging.
So how do you offer your solutions to your customers? Do you write installation scripts using STSADM commands? What other options do we have?
I would ship a .zip file which contains
install.bat performs the deployment of the solutions by making calls into STSADM.EXE
We have build a complete framework in PowerShell for deploying solution packages, with pre-/post-configuration events, definition of relation between modules, rollback (if implemented in callouts) and even partial updates.
It basicly wraps STSADM but adds the possibility of configuring stuff before or after modules are deployed (like setting up BDC application and rights programmatically before deploying custom BDC web parts).
It was alot of work, but the result is pretty nifty.
Wsps with a batch file. this batch file will use stsadm commands to add and deploy solution. also feature activation can be specified in the batch file.
We're developing web parts using log4net as the logging framework. Right now we're leaving the configuration details in the web.config and will be moving the log4net.dll to the GAC manually. For a small development team (2 devs) and an internal sharepoint installation, is that adequate? I've read about using WspBuilder, creating a setup project, a globablly scoped solutions, and so on for deployment but We really aren't going to have that much custom code. Most of our sites will be using out-of-the-box or third-party web parts along with Enterprise features like the Business Data Catalog
In our SharePoint solution we need a service which can search and index XML files. At this moment we are using FAST, but are there other tools / applications / solutions which are free and easy to integrate / customize within SharePoint 2007 ?
providers). I have even responded to some of them. Custom site definition to define a custom site with a subsite Best way to build out and configure multiple lists When to use Custom Site Definitions... and not There are a few rules of thumb to go by (resources, permissions, ease of deployment, granularity of control). One thing that has to be considered, though, is how do you propogate... get mixed signals because the Microsoft developer exams seemed put a lot of weight on site definitions and templates. So, what are the best practices for modifying your sites/lists after they have
. That won't look good for her. Other than that, I upgrade her hosting package which she won't for right now and I can create a more custom solution. What do you recommend? ...I am working on writing up a concept for hosted Windows SharePoint Services environment through FPWeb for a potential customer. Here's my scenario. Using a basic package (cheaper) to start off... website. Since we're starting off with the basic package I cannot install my own custom WSPs to handle this, instead I have to rely on SPD and out of the box SharePoint functionality. My issue
I am using SharePoint 2007 Enterprise with Windows Server 2008. I am using VSTS 2008 + C# + .Net 3.5. I am new to SharePoint user control development and deployment. I am learning from, http://www.codeproject.com/KB/sharepoint/PageFooter.aspx But confused about the following deployment steps, my question is in what files do I need to modify to insert the following code segments? Register your control: <%@ Register TagPrefix="Flygare" TagName="PageFooter" src="~/_controltemplates/PageFooter.ascx" %> Insert your control: <Flygare:PageFooter id="PageFoot" runat="server
Problem: Multiple solutions using shared dll's can cause havoc when individual solutions are retracted. Example: You have a web part helper dll used by all your web part code. If you retract a solution containing a reference to this dll then the SafeControl entry is removed from the appropriate web application and all your web parts start to fail. Or even better, the dll is removed from the GAC altogether. Solution: I don't know? You tell me.
How can I set a web part so it will be automatically appended to a web part zone when a specific page layout is selected? The solutions I have tried so far is: Using <ZoneTemplate> under <... the page. We do have hooks for setting default page layout based on where in the structure the page is created, here we can append the web part as well, but then the web part will only be added if you create... programmatic when creating site structure (deployment script) Add a hook that hooks in and adds the web part Problems with the solutions: The web part seems to become static, and can not be removed
I have come across blogs about how to setup an external content type. For example: http://www.dotnetmafia.com/blogs/dotnettipoftheday/archive/2010/02/02/it-s-easy-to-configure-an-external-list-with-business-connectivity-services-bcs-in-sharepoint-foundation-2010.aspx But I have not seen any examples of what to do when your external SQL DB has foreign keys. For example. I have a database that has orders and customers. An order has one and only one customer and a customer can have many orders. How can I setup external content types in such a way that when in the list view of these external
I'm pretty new to sharepoint-development, so I thought I'd check real quick with the gurus in here. I've been given the task of building a replacement for the built-in Alert Me feature. The main reason for this is to allow for alerting members of a role with a forms authenticated sharepoint. This is where you guys come in. I know you can build an immediate Alert Me function by creating list item event receivers. However, if I wanted to create the summary-feature (daily/weekly notifications) - what would be the best way to go about this? With very limited knowledge, all I could think