Is there a tool or method/process to create a package which installs multiple WSP files using a single setup for both SharePoint 2007 and SharePoint 2010?
I don't think there is any setup tool out there which can deploy multiple wsps. So I wrote a custom setup to deploy them.
Related
Trying to publish a click once type app to a local directory and create a websetup with the published contents- so that i can give tat setup to install in two different servers. but as the publishing wizard takes a URL - separate setup is required for each server. Is there any way that i can create a single setup which i can use it in two servers..?
The URL for setup.exe is only for the purpose of bootstrapping. What I found is that the bootstrapper that gets created with your deployment manifest ('setup.exe') is designed for a web-published application.
If your clickonce publish will be installed on intranet servers, you can't use out of the box bootstrapper. You may write your own or build a seperate setup project for bootstrapping and calling the .application from the installed server when the pre requisites where installed.
If you don't rely on pre requisites and you can ask users to make sure they have the right CLR version, you don't need the setup.exe at all.
A web application is installed on our sharepoint server. I have the WSP and dll files for the solution but not the source code. I need to make some changes in the code of the webpages of that application so I have to create a new web application with exact same functionality from scratch so that I have full control. How can I use the WSP and DLL files to create a new solution.
I have imported the WSP package in vs2010 and decompiled the dll file to get code behinds of aspx pages.
You can give a shot to tools that reflect on code. You will be able to generate a lot of code OOB using ILSpy. Give it a shot.
File C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Extensions\Microsoft Corporation\NuGet Package Manager\1.5.20902.9026\Modules\NuGet\profile.ps1 cannot be loaded because the execution of scripts is disabled on this system.
I would like to piggyback another :
Why does a new MVC4 project not come with a unit test project? It is not letting me check the box for that.
And one more thing : why is it not including the MicrosoftMVCAjax scripts in the scripts folder?
I am finding I can write a working JSONapp with partial views and callbacks if I have this one from an older MVC2 or 3 project.
Thanks!
You should be able to create check the unit test project check box for the Internet and Intranet project templates.
We are de-emphasizing the use of Microsoft AJAX scripts in MVC templates and instead focusing on the jQuery family of scripts. However, you can still use the scripts if you copy them from an existing MVC 2 or 3 project.
What I currently need is to programmatically make certain changes in existing wsp file. Most likely wsp file will be created using "Save site as template" SharePoint action - and I'll need to update it.
What api/approach would you recommend to accomplish this task? Please note that .NET C# is mandatory. Some approaches/questions I could see now:
Do you guys know some 3rd party tool allowing "friendly" object model to work with WSP files? I could not find one.
Do you know is there any special assemblies that could be used for this in WSPBuilder or Visual Studio 2010?
What CAB tool would you recommend? Because it seems there are not so much .NET solutions to work with CAB files.
You can use cablib.dll . Its the same API library which the WSP BUilder uses.
Note that making changes like this programmatically is not recommended and by deploying it might put your server into unsupported mode.
http://www.codeproject.com/KB/files/CABCompressExtract.aspx
I have various IIS hosted service hosts with simple svc files etc. What I want to do is to be able to create deployment packages from our test server using IIS Export Package in a way that parameters may be saved and picked up at Export time so that the Export is repeatable and automatable. I.e. the Export will always use the necessary Manifest extensions such as XmlFile etc.
The web sites exist in the solutions and are then picked up using a Web Deployment project in each solution so that config substitutions are done etc.
We are currently on VS 2008 SP1 so do not have direct access to VS 2010
The first issue I have with MsBuild (running in TeamCity) is how to build the IIS web site (with target=Package) when there is no project file? In this way maybe I can avoid the Web Deployment projects (I use them for various configurations but don't want to do it this way for deploying to Production but rather export from our fully tested staging into a package file to be imported onto a production server).
Secondly, I want to avoid having to configure the Export in IIS 7 each time I run it. I want it simply to pick up the correct set of extensions to use and create the necessary parameters for me. Is this done from a Manifest file? I can see how to use the parameters.xml but I am unclear whether I need to use a manifest.xml (created by hand) and how to link it in. The idea is that a tester/deployment person should be able to do the Export simply without having to enable all of the extensions that are required
Any help or guidance will be greatly appreciated.
Ok, in the meantime I got it figured out.
I ended up using the document at Package an Application for the Windows Web Application Gallery which gave me the means by which I could extend our automated build in TeamCity to create the "repeatable" export packages.
In short I will use the current Web Deployment Projects to create the deployment artefacts and then in MsBuild combine them with the pre-prepared manifest.xml and parameters.xml files into Build artefacts folder and zip them up into a package. From there the task will be to Import the package into IIS Deploy in the target environment.
The parameters.xml file will be used to set the HostName for wcf clients and services, connection strings, app settings etc.
This turned out to be the best solutuion bcause I can put it into our automated build.