I am using Windows Vista Ultimate and I want to install Umbraco CMS, with which I have no previous experience.
Common installation methods i.e. Installing either via Microsoft Webmatrix or Web Platform Installer didn't work for me. The former is for 7 and 8 versions of Windows and the latter downloads all installation files but fails to install. That is it shows "Installing ..." dialog for over 3 hours that makes me to forcefully end the installation. So all efforts have to be done from scratch (including download of the installation components using Web Platform Installer).
Is there a way to manually install Umbraco without the help of Platform Installer? I have downloaded seperately the files needed for Vista(e.g. Umbraco 7xxx.zip,Powershell 2, ASP.NET MVC, etc.). I don't see any executable in the package for Umbraco. There are just DLL's which I don't know where to copy to, as well as many aspx and ascx files that I don't know what to do with.
http://our.umbraco.org/contribute/releases shows the latest and all other available umbraco releases.
Under the 'Current' heading, you will find links to the most recent stable release detail page where you can grab UmbracoCms.X.X.X.zip which are all the files you need to go through the process manually.
One of the absolute best things about umbraco is that it's so easy to spin up a new isntall this way!
Important! Before you unzip - be sure to right-click the .zip file and open the properties page.
There will be an option to "Unblock" - be sure to click this or you may well experience issues with the dlls.
Unzip these files to where your webroot will be, set-up your IIS site and open in your browser - umbraco will automatically pick up that you need to do 'the install' and take you through a few simple steps that set-up the database and your admin credentials. There are no exe's or installer files - it's all embedded, more-or-less, in the site.
A good practice is the remove the [/install/] folder once you've gone through these steps.
Umbraco has some installation documentation here if you want to see all the various ways and steps available to install an umbraco site. -I prefer the .zip way described above, but you can also go the NuGet route too.
Related
I have created a WIX Install MSI file for my Office Outlook Plugin. Everything runs fine however when i uninstall it through add/remove programs everything is removed except for the Plugin in Outlook. It runs but gives errors because the other components are now missing. How can I get it to remove it without going to Outlook and removing the plugin manually?
I have added the "RemoveFolder" tag in the XML which has no effect.
I'm guessing that you are doing some kind of active setup trick to do HKEY_CURRENT_USER registry propogation. I'd suggest not doing this and instead register the extension in HKEY_LOCAL_MACHINE. This way when the uninstall runs it can access all of the components that need to be removed. There are gotchas in terms of different patch versions of different versions of office and how they behave in terms of supporting per-machine registration of AddIns. Details can be found in blog articles that I've written over the years titled VSTO lessons learned.
I installed WeBlog package from sitecore marketplace (http://marketplace.sitecore.net/en/Modules/WeBlog.aspx) in my sitecore instance. Initially i had trouble installing package however i retried again deleting weblog.config file. It installed without any issue however when i look into content editor i don't see any WeBlog Modules under Template, System or Layout sections.
Does anyone know why?
Thanks.
Which version of Sitecore are you on? Is the module compatible? Weblog shows that it's compatible with the following versions: CMS 6.2, CMS 6.3, CMS 6.3.1, CMS 6.4, CMS 6.4.1, CMS 6.5.
Assuming you're on a compatible version, I'd check to make sure the layouts and sublayouts that were in the weblog package were actually installed on your instance. Open up the zip file and check out what files should have been installed.
Failing that, have a look at the log files to see if there are any glaring errors.
As a last ditch, you may want to try publishing. It shouldn't really matter in your content editor view, but I view the "publish" feature of Sitecore like the "reboot" feature of Windows.
I'm working on a VSTO add-in for Outlook, versions 2007-2013and minimum .Net version is 4.0. In my project I have a couple of referenced libraries. When I deploy the add-in via MSI (built via Wix) the add-in itself is loaded into Outlook but, the referenced libraries are not available.
It works fine on my development machine so I'm assuming it is a trust issue of some sort. I am uncertain as to what needs done to have the included libraries themselves be trusted. Any help is appreciated.
Are you using VS setup project for addin deployment? If so, you might want to try
Right-click setup project icon => Add => Assembly...
to add your external libraries.
Regarding the trust issue, please take a look at these articles on MSDN. Inclusion list might also be helpful in your case.
Also, to test deployment on your development machine, I'd suggest you clean your project/solution first
Right-click Project/Solution icon in Solution Explorer => Clean
then deploy and install your addin onto your machine.
Situation: I've already written an ActiveX control for my IE users which works perfectly. I build the .ocx, CAB it up, sign it, and put it on the site with an EMBED tag. Users load the page, the yellow bar shows up asking if they want to install it: all they have to do is click it, and we're off.
Now I need to build support for FF, Chrome, and Safari (on Mac). From my research, NPAPI is the way to do this, and Firebreath is supposed to make it easier. But from what I have read, deployment is not so easy. Windows users would have to run "regsvr32" on a DLL (which none of my web users would actually do). I have no idea what would happen on a Mac. I believe the user has to copy it to a directory like /Library/Internet\ Plugins/, which is also a non-starter for deployment. Firefox users would download/run an .xpi. Chrome is supposed to run a .crx.
Does anyone out there have experience with this? How do you do a easy-for-users-to-run deployment of an NPAPI plugin for the other big 3 browsers?
This is a question that is raised a lot by FireBreath users, so it's probably about time I responded in more detail on a forum that is easier to find than the project google group.
First of all, to clear up the regsvr32 thing, FireBreath does indeed support "self registering" for all browsers; that means when you call regsvr32 it installs registry keys not just for IE but also for NPAPI browsers using the methods linked to by DReJ (+1 for that info, btw, thanks. Many don't know where to find it).
However, self-registering DLLs is highly discouraged in the installer world and by Microsoft. There are a lot of reasons for this. You've done a pretty good job of summarizing the other install options in your post; You can use a .cab on IE and a .XPI on firefox, but of course those don't help you on other browsers.
The method recommended by the FireBreath team (which I lead) is to use an MSI installer for all browsers. Personally, I dislike having things work differently on different browsers for an install, so I use javascript to detect the presence (or absence) of the plugin and then prompt the user to download and run the MSI installer.
FireBreath has "built-in" support for building MSI installers with WiX. If you install WiX 3.0 or later on your machine and re-run the prep script it will create a _WiXInstaller project that will build a basic MSI to install your plugin for all browsers as part of the Visual Studio build process. You can modify the .wxs template that will be left in your home directory to customize it.
More info can be found on the FireBreath wiki:
http://www.firebreath.org/display/documentation/WiX+Installer+Help
http://www.firebreath.org/display/~me#iaincollins.com/Potential+Installer+Improvements
If you are really in love with using your .cab installer for IE (I've had problems with them, but some seem to have good luck with them) you can distribute the MSI file inside your CAB and have it run when the CAB is installed. The advantage to this is that when you install the MSI it installs everything for IE, Firefox, Safari, Chrome, and Opera (as well as other browsers which are compatible with the same plugin technologies that those browsers use).
As a quick note, the reason that an MSI is the ideal solution for installing plugins (as opposed to using something that calls DllRegisterServer like regsvr32) is that the MSI is transaction based, so when you uninstall it will always reverse what was put in; that means that you don't have to worry about supporting uninstalling 10 different old installer versions that put things in different places, etc, because the MSI system takes care of uninstalling everything cleanly when you upgrade.
Hope that helps!
For NPAPI plugin you shouldn't run "regsvr32", in Windows you need to write some stuff to the register and on Mac or Linux you need to copy the plugin to specified locations (see "Installing Plug-ins"). I think the easiest way to deploy NPAPI plugin on Windows is to create windows installer that will install both activeX and NPAPI versions of the plugin (for example, you can look how deployment is done for commercial plugins like Unity3D, Roozz or Silverlight). The same is for Mac - just create installer.
I'm not aware of any way to install a plugin from within Safari.
Also, keep in mind that while you may think of the extension-style deployment as easier for users, it's not all that uncommon for Mac users to use more than one browser. If you make them re-install your plugin in each browser they will be confused (since that's not how browser plugins are generally deployed on the Mac) and annoyed. An installer or a manual drag-and-drop installation are the standard ways of deploying plugins on the Mac.
For .net 3.5 SP1, Microsoft have the new client profile which installs only a subset of .net 3.5 SP1 on to Windows XP user's machines.
I'm aware of how to make my assemblies client-profile ready. And I've read the articles on how to implement an installer for ClickOnce or MSI.
But I've been using Inno Setup for my project so far and I'd like to continue to use it (as an Express user, I can't easily make MSIs), I need to know how to use the client-profile installer in a custom environment.
There is an article on a Deployment.xml schema, but no indication of how to write one, package it or anything else. Can someone explain this process? Finding the articles I linked to alone was a painful search experience.
Microsoft has now shipped the Client Profile Configuration Designer (Beta).
This designer lets you edit the XML files with some limitations, this isn't a 'Google beta' by any means.
Information and download
Can you clarify: Are you trying to write an installer for your app, which depends on the Client-Profile, or are you trying to write a custom installer for the client-profile?
I haven't used it personally, but if it's anything like the dotnetfx 1 and 2 msi's, you basically have to just invoke it's executable yourself from your own .exe file, or from an Msi BEFORE the InstallExecuteSequence starts up - you can't "embed" those in your own app, MS go out of their way to tell you not to do that due to suckage of MSI.
Client profile works only on clean XP. If your user as .Net 1 or 2 installed, client profile wont install...
You have an offline version (integrating Full .Net3.5 Install in case Client Wont install) 200 to 300Mo don't remember
Online version will get required files.
You can call a silent install from the first steps of your install.