I was wondering, if I deploy a WSP using the stsadm command:
stsadm -o addsolution –filename myWSP.wsp
Will this also install the required DLL's (already included in the WSP) into the GAC?
Or is this another manual process?
This is determined by the DeploymentTarget attribute in the solution's manifest.xml. If you are maintaining this file yourself, using the following syntax will deploy the code to the GAC:
<Assemblies>
<Assembly DeploymentTarget="GlobalAssemblyCache"
Location="MyGAC.dll" />
</Assemblies>
If you are using a tool to create the solution, it depends on the tool. WSPBuilder defaults to deploying to the GAC however it can be configured otherwise. See the "Scoping the assembly for BIN instead of GAC (including Code Access Security generation)" section of this article by Tobias Zimmergren for steps on how to deploy to bin.
If you're building the packages via VS, open the Package and click the Advanced tab on the bottom. You'll be able to add additional assemblies and specify the Deployment Target from here. I'd strongly recommend doing this rather than updating the XML directly...but that's just me.
As the command says addsolution it is just going to add the solution to the Solution store. You need to call the command deploysolution to get the stuffs to place. Here is the command that you need to call
stsadmin -o deploysolution -name [solutionname] -allowgacdeployment
Note that allowgacdeployment is mandatory to place the files to gac. you can more help on this command with this
STSADM.EXE -help deploysolution
There is an alternate option to get this done,through UI. Go to Central Admin -> Operations ->Solution management select the solution and say deploy. this will be easier way to get it done quick.
Related
I have an InstallShield project which consists of two files and several folders,
MainSoftware.exe
AuxSoftware.msi
FolderA
FolderB
etc...
The main purpose of the project is just copying all of these files in the path specified by the user. It is very simple. However, after copying AuxSoftware.msi in the destination path, I need that a silent installation begins with this file. I know that a silent installation can be run by the following command:
msiexec /i AuxSoftware.msi /qn
But I don't know how to tell InstallShield that this command must be executed in the destination path after copying AuxSoftware.msi.
Could you please help me?
Thanks in advance
You can only execute one installer at a time once it is in the InstallExecuteSequence. Stein has a very good, brief explanation in the answer here.
I would suggest using a bootstrapper (setup.exe) that can install them in sequence.
Thanks for your suggestions. I found a way. They call it "nested installations". I created a Custom Action having the second .msi or .exe installer I want to run after a specific point in the process of the main installation.
After executing the below commands using one of the recipes available in the standard hybris 6.4 package, only hAC is accessible, but the frontend, backoffice and hMC are not. If I try to open, e.g., the backoffice, it gets me to hAC.
These are the commands:
install.bat -r <recipe> initialize
install.bat -r <recipe> start
What do I miss to make the above components available?
Can you provide some more information about - generated localextensions.xml. Also, can you check if the workspace contains models (signifying the ant clean all was completed successfully)
Also, please go to HAC->Platform->Extensions and see if the backoffice, storefront are deployed.
Sometimes, the installation recipe does not functions correctly due to which some installation steps are skipped. You are advised to do ant clean initialize and check again.
Please let me know if you still face issues.
Cheers!
Hi I have a visual studio solution which has been configured in Jenkins. And it's building successfully in debug configuration. How ever I need to change the build configuration to Release or another different one.
So How can I configure Jenkins to select the configuration to build?
If you are using the MSBuild plugin, try adding the configuration flag on the "Command Line Arguments" section:
/p:Configuration=Release
If you are simply building from command line script (batch, powershell, etc), add the above flag there..
What I do, is create a generic job for build process which receives a parameter called "BUILD_CONFIGURATION" from the parent job which triggers it.
And I then reference it in the flag as a variable:
/p:Configuration=${BUILD_CONFIGURATION}
I'm trying to figure out how to run a pre/post command using the deploy.cmd generated by VS/MSBuild. I understand there are pre/postsync commands which can be set on the command line with msbuild but this is fixed within the web deploy package inside of the x.deploy.cmd.
How do I go about customizing the output of this file so that I can run the deploy command with specific parameters?
The intention is a non-developer will pick up the package zip file and import the application into IIS. We use IIS to host some windows services and so to be able to deploy we need to stop and uninstall the service before deployment and then install restart in the post deploy stage.
For certain servers we allow auto deployments from TFS and hook this pre/post command using the .targets file of the msbuild WPP pipeline. However, we want to this to be available to the manual deploy command files.
PreSync/PostSync are features of the msdeploy command line and are not supported by the package/manifest providers, or even the API. They are equivalent to running msdeploy a second time, so there's no way you'll be able to include their functionality while directly importing the package into IIS.
I'd recommend having a batch/powershell file on the server that the user runs after copying the package into the same directory.
The .cmd file that MSBuild generates is boilerplate script that you can simply change to call your pre/post powershell scripts. Just overwrite the one generated by the build with your custom one.
So I have used the following command to deploy a solution to SharePoint as I am a new commer to SharePoint developement.
stsadm -o addsolution -filename Demo.wsp
I used WSPBuilder to build the wsp file which just contains one web part. What do I do deploy the new wsp file. When I try using the same command above I get the error.
a solution with the same name "Demo.wsp" or id "blahblah" already exists in the solution store
Use stsadm -o upgradesolution -filename <localwsp> -name <solutionname> -- but remember that the solutionid must be the same for both the new and the current WSPs (this is normally the case unless you're doing something a bit weird.)
-Oisin