Can a app developed for Outlook 2013 containing HTML, CSS and JS files (jQuery, Office.js) be deployed in a production environment by running an MSI?
I have read the resource available in MSDN - http://msdn.microsoft.com/en-us/library/office/fp142256(v=office.15).aspx
This resource talks about test deployment. However, I could not convince customer to follow the same approach as they are demanding an MSI file with COM add-in installation procedure in mind.
I want to confirm if I am overlooking any option available for production deployment.
Please help!
No, you can't deploy Office Apps using MSI.
Related
I have developed a custom sharepoint 2010 action and succesfully deployed through wsp
ADD-SPSolution, Install-SPSsolution + modification of web.config for port 80 and deployment was successful and I see this action also in Designer and action can be used within workflow.
I need to deploy it to Sharepoint 2013 foundation workflow platform 2010, so I used the same process, deployment to GAC, GlobalDeployment, compatibilityMode 14,15.
I also added authorized type to web.config, but I can not see activity in sharepoint designer 2013.
I created developement server Sharepoint 2013, I have created the activity on this new dev server and succesfully deployed to dev server, but despite this, I can not deploy it to production server as mentioned at the begining of this paragraph.
The only difference is that developement servers (SP Foundation 2010/2013) use PORT 80 /HTTP/ and production server uses port 443/HTTPS.
Is there any difference when deploying to this web aplication with SSL/TLS configured? Do I need to modify somehow source code? Or installation process?
I have lost 2 days and I have seen probably all forums in the web...
Kind regards and thank for help upfront.
This might be silly, but have you activated the feature that contains the workflow activity on the particular production site? SPD reads from the site.
Close SPD.
Check your %LOCALAPPDATA%\Microsoft\WebsiteCache and %APPDATA%\Microsoft\Web Server Extensions\Cache - clear out the site that your SPD has cached and then restart - see if SPD brings down the site definitions again.
I recently implemented an Outlook plugin for my enterprise and now I want to deploy it to all of the users on the enterprise. Is there a way to deploy the add-in installer to all of the users on the Active Directory, maybe using Outlook Exchange?
I checked this page, and looks like the guys at commvault nailed that.
Any ideas?
You can't deploy add-ins via email with Exchange, if that's what you are hoping for. If your add-in is packaged in a Windows Installer setup file, then you can use traditional Windows Desktop Application deployment methods to distribute your add-in.
I have a smart client app (WinForms/WPF) currently deployed using ClickOnce.
A particular client has expressed the desire to silently deploy the app to it's intranet network users as part of its nightly/weekly client PC update service - presumably via MS Systems Management Server (SMS) and Group Policy or similar (I don't understand the exact mechanisms). As such, they've requested a .MSI installer instead.
So a few questions for confirmation (along with my thoughts on answer - am more than happy to be wrong!):
Can a ClickOnce app be silently installed en-mass by admin???
My thoughts: No, because ClickOnce is a per-user installation this would be difficult unless the user is actually logged in at time of remote installation.
Is there a tool to convert a ClickOnce app/project's settings to a simple MSI installer project (e.g. Visual Studio Deployment Project)???
My thoughts: Not in the box, but would love a tool to repeatedly copy/use settings from the ClickOnce config to the deployment project - e.g. ProductName, Version, File Associations etc. This way we only maintain one set of deployment settings.
Any other alternatives for this scenario to get 'er done quick...?
I don't think you can install a ClickOnce application silently, certainly not with SMS. And I don't know of any tool that does that, but it doesn't mean it doesn't exist. ;-)
The idea of deploying a shortcut is an interesting thought. Have you ever noticed that if you leave a shortcut on the desktop even after the application is uninstalled, if the user clicks on it, it reinstalls the application?
With VS 2008 I always used Web Deployment Projects to build to three different environments. It is maybe not the best solution, since I still have to xcopy the built files to the server, but it is simple.
Now with VS 2010 it looks promising, but it also looks complicated. My hosting provider doesn't have Web Deploy, the newest feature and the flagship technology for deployment in VS 2010.
My question is how can I just build for each environment and copy the files over to the server? Using the Build Deployment Package will create the ZIP file and when I extract it, it will output so many files and a confusing folder structure. Does anyone have any suggestions?
There is a release of Web Deployment Projects for Visual Studio 2010. The Beta 1 release [is available][1] from the Microsoft Download Centre.
This was mentioned on the Visual Web Developer Team Blog too.
Just went from TFS 2008 to 2010 at a client site and now wondering what happened to the TFSBuild.proj files from the TeamBuildTypes folder. I've already got the builds and drops working and now I need to get the old deployments working again. We used to do this with AfterBuild targets in the TFSBuild.proj. That mechanism seems to have moved or disappeared in 2010.
Can anyone point me to an article or describe how the deployment options have changed in 2010?
Specifically, I need to support running psexec to install and enable Windows Services on remote deployment targets and I need to deploy some web sites / web services to remote IIS nodes as part of the automated builds.
EDIT: Just found this: http://blogs.msdn.com/jimlamb/archive/2009/11/03/upgrading-tfs-2008-build-definitions-to-tfs-2010.aspx I'm more than a little taken back by the breaking changes between 2008 and 2010. I'm gonna need advice on how to deploy remote sites and services in the new default build process template mechanism.
Check out Vishal Joshi's PDC talk on Deploying Web Applications with VS 2010 and MSDeploy. On his blog, you'll also find tips on building MSDeploy packages with MSBuild. You can run psexec from your MSBuild script or, potentially, from a customized build process template. With TFS 2010, you can use MSBuild and Windows Workflow to solve your build automation problems.
Alternatively, you can use the "Upgrade" build process template and continue using your TFSBuild.proj file. This is the default behavior for upgraded build definitions for backwards compatibility. In that case, your build is still primarily driven by MSBuild with just a thin workflow to allocate an agent and run MSBuild.
Another option is to use TFS 2010 Build Agent on the server that you deploy to. This is how Visual Studio Lab Management deploys.
I have written a blog post about this: Continuous deployment with TFS 2010 Build Agent