Tag Info

Hot answers tagged

12

CruiseControl.NET, NAnt/MSBuild, WSPBuilder and some PowerShell scripts along with a virtual machine. Cruise kicks off the process where the VM starts up from a template and the scripts/solutions are deployed (via a network share). The VM runs automated scripts (Selenium) to automate some tests and report back out to Cruise (and other tools). The entire ...


4

Use a pre-build event (not post-build!) as described in: http://msdn.microsoft.com/en-us/library/ee538587.aspx


3

Here's our setup, if that can help you with ideas on getting your setup like you want it: Build Setup We use TFS for builds with the following setup: Nightly build for DevTest Manual triggered build for SystemTest. Depends on DevTest Manual triggered build for UAT. Depends on SystemTest Manual triggered build for Production. Depends on UAT Depends here ...


2

I'd say the biggest is that you greatly reduce the potential for human error. Say there are ten steps that you take for a deployment. If it's a person doing them, then it's likely they might forget one or do one incorrectly. With an automated process you can be sure that it's doing the same thing every time.


2

You can use the $(SharePointSiteUrl) variable in the post-build event. $(SharePointSiteUrl)is an extra variable that is available for SharePoint projects. $(SharePointSiteUrl) is the URL you’ve selected in the properties of the SharePoint project. $(TargetDir)$(TargetName).wsp is the name of the solution package file. For flexibility, ...


2

As a newer answer, we're using Visual Studio test lab management to spin up Hyper-V snapshots. Once they're up, the system is installed/upgraded using a custom deployment application launched from TFS Build. We haven't got automated tests working against the deployed system quite yet, but that's the general plan.


2

Running Build in Visual Studio will generate/create the assembly. Deploying it will simply register it with the SharePoint platform. Update: As David added, the "Deploy" command in Visual Studio does also trigger the build event before it is deployed to SharePoint. The act of deployment within SharePoint though, simply registers it with SharePoint.


2

According to this blog post the only solutions are to: set the project's PlatformTarget properly ignore the warning set ResolveAssemblyWarnOrErrorOnTargetArchitectureMismatch property to None in your project file.


1

Hotfixes do not update core version numbers so even having the same hotfixes applied does not mean it is the same version. According to the SharePoint Build Numbers, it your Test environment is on Feb 2012 CU while your Prod environment is on the Apr 2012 CU. Having difference CUs applied in the various environments is never a good thing for development. ...


1

It will likely be a lot easier to develop these as 2010 sandboxed solutions and deploy them to the 2013 site. Almost all 2010 solutions still work in 2013 and it even still has the 14 hive. If you need to develop each as an app that will be a little more work but that is not required for it to work in 2013. Even then an app is mostly packaging around a ...


1

Running Deploy in VS will build it, compile the package WSP file, then deploy it to SharePoint.


1

You can try Alexander's PowerShell link but if you want something really easy and quick which will enable you to get assembly you want from gac then you can try this, Click start and then on "Run", Put this command in it, %windir%\assembly\GAC_MSIL // you move back a directory it will show you gac as folders which you can copy and that. If your ...


1

It looks like you can collect assemblies from the dev environment by PowerShell script. And then install them to the build server. You can modify this script to retrieve all needed assemblies.


1

Visual Studio creates the WSP at build since it includes this in the CSPROJ file: <Import Project="$(MSBuildExtensionsPath32)\Microsoft\VisualStudio\v10.0\SharePointTools\Microsoft.VisualStudio.SharePoint.targets" /> That does a lot of work to validate the project and such before creating a WSP file. If you simply build the project with msbuild, ...


1

It works quite nice with command below msbuild /t:Package <YourProjectNameHere> /p:Configuration=Release /p:Platform="Any CPU" /p:OutputPath=<OutgoingPath> Please also check this post http://social.msdn.microsoft.com/Forums/en-US/appsforsharepoint/thread/34fad52e-31fa-400f-ba94-dbfd97a7cc43


1

I'm doing a similar thing in MOSS, and I'm trying to use PowerShell as little possible - for the simple reason being that I believe (for MOSS2007) command line windows batch scripts (for stsadm) are more terse than powershell (as a coder I go for brevity every time). My script runs in two stages actually - one goes around and collects WSPs, and separate ...


1

This sounds like a good solution to me. You could put it in a single SharePoint solution but honestly I like your approach. Are you accounting for updates or only fresh installs? Also do you handle rolling back the deployment if one of the deployment steps fails? The only thing I noticed that you may want to change is to make the load initial data optional ...


1

Chris O'Brien and the SharePoint Dev Team have a blog post series on automated builds and testing. I don't have links to all the articles in the series but the last one can be found here. Chris and Mike Morton did a talk on the subject at the most recent Microsoft SharePoint Conference. The video recording of the session is available for those who attended ...


1

UAT should be considered disposable in terms of content. It's there for testing, not for live content authoring. You should not need to 'migrate' content from UAT to Live, but you can have a regular backsync of content from Live to UAT, such that recent functional changes can be tested with 'recent' content. The publishing approval features of SharePoint ...


1

This question has already been asked in SE. Team Foundation Build or TeamCity? TeamCity vs Team Build


1

There are multiple types of artifacts when working for SharePoint - which makes it "special". Sticking to the "Branding & Design" artifacts these are different because they would "complete/extend" SharePoint so you can see it as: You need to deploy additional artifacts (CSS, Master Page, Page Layouts - for Publishing sites or Web Parts page for ...


1

Dan, Per answered your question. But, a helpful fyi: In your project, rightclick the project name and to go properties. You'll see a SharePoint tab. Click there. There is also a list for grouped deployment options. Click into the default item. There, you'll see the actions (scripts, either cmd or ps1) that visual studio performs when you click "deploy". ...


1

A SharePoint Solution (WSP file) is a compressed (.cab) file which contains all of your files (including dlls) and a Manifest.xml telling SharePoint about which files and Features is included. "Deploying" this Solution to SharePoint is in fact a two step process Add the Solution (which stores a copy of the WSP in the Configuration Database) Deploy the ...


1

@Daniel McNully I have been working on a custom master page and web parts for a couple of weeks now and the way I do it as follows: Deploy to a web app (either sandbox or as farm; since I am on a dev environment, I deploy as a farm solution) and to answer your question, Yes every time you make any changes in the solution (I am assuming you are using Visual ...


1

Automate as much as possible, especially when it's a repeatable task. After all, if you're going to have to do it on Dev, Test, Staging and then the Live environment, you might as well ensure that the same action is being done on all. If you have access to Powershell, try wrapping deployment tasks in that. Other options are command line tools or features. ...


1

In addition to the advantages of automation, having a separate build server verifies that everything you need is in source control. Development environments tend to end up with forgotten dependencies. You need to be able to build from source control in a clean environment. Of course, all of these considerationss apply to software development generally, not ...



Only top voted, non community-wiki answers of a minimum length are eligible