I am just getting started with Wix. I see there there a several libraries included with the default Wix install. I also see that users can create their own libraries(wixlibs). Are there any 3rd party Wix libraries out there that add additional functionality to Wix that may not come packaged with the default install?
check out AppSecInc I've used their wix libraries and ui dialogs and they are pretty awesome
a quick Google search doesn't really return a lot of good results, so I'm guessing there aren't a lot out there right now. Anytime we want to do something special at our company, we use Custom Action dlls (which can be made in .NET code).
Related
I have been working with Wordpress and Drupal for a while now, and something you have to do to maintain those CMSs is update themes, plugins, core, and modules.
My question is do you have to do that with the ExpressionEngine CMS? In the addons dropdown, there are modules, accessories, extentions, fieldtypes, and plugins. When I go to these, it doens't look like there is a way to update them. It shows what version there is, and I am able to delete them from there, but no updates anywhere in sight. Is it something I even need to do?
Thanks
Edit: I found the "update modules" button, but I still do not see anything like that for plugins, or anything else.
EE doesn't make it quite as easy as it is in WordPress. You could check out the Lamplighter extension to see what's still in need of an update then download from the respective source.
This is getting into opinion a bit but when I did a lot of EE dev, I usually stuck to the philosophy that if it worked, I used it and didn't worry about upgrading. Occasionally an extension/plugin would get a significant upgrade, a security patch, or have a feature implemented that I needed. That's That's when I'd go through the process of downloading and installing updates.
I have started using Git for my other development projects (PHP, HTML, JavaScript, etc.) and can now see how beneficial it is, however I've been unable to find anything similar for Dynamics CRM 2011/2013 as a lot of the solution development is done within the web interface.
I'm guessing this is not possible, but could someone with more experience than me please confirm this or let me know which tools I should be looking into?
Thanks
You can use the Visual Studio Developer Toolkit available in the SDK to version control your plugins and web resources initially. I'd recommend this as your first step.
If you choose to take it further you can also look at using the SolutionPackager tool to version control your solutions. This will split out your solution zip file into separate version controllable files for each component. It works best when you follow the developer workflow outlined in the linked MSDN article
I am new to sakai, i want to add my own tool in sakai source code like announcement,syllabus...etc That tool having some my own functionality for this what i have to do, how can i develop my own tool in sakai.
Thanks.
Use one of the archetypes to get you started, then customise it. When you are comfortable you can change the UI layer to be whatever you like.
https://confluence.sakaiproject.org/display/BOOT/Developer+Tools
If you are looking for a solid "base" tool shell to begin with tool development my recommendation would be to start here: "Sakai Wicket Maven Archetype". There are a few other very good archetypes available but are often outdated and may cause you some problems based on my experience. This has been the one I've had the most success with.
This uses Wicket but does not mean you have to use Wicket to develop further with it. Make sure to pull the 1.2 version as last check the binaries for the others were not available yet so replace -DarchetypeVersion=1.4.1 with -DarchetypeVersion=1.2 It will compile and deploy successfully as a tool "as-is" that you can modify as needed. It also allows you to code in Java to directly access the sakai API and pull from its database or even add your own tables. I've successfully used it with NetBeans 8.0.1 and MySQL 5.6 under Windows 7 with Maven 3.2.3 and Sakai 10.1.
The code is well-documented and is no-frills but with enough varied functional use examples to allow you to do "almost" anything you want. The wicket manual is 600+ pages but in my experience you should be able to accomplish a lot just by looking at the code in the archetype.
We've decided to create a custom bootstrapper for our deployment solution. We are currently re-writing and re-designing our deployment strategy for all of our products. Sadly, none of us are deployment experts.
Here's what we have so far:
A. The MSI packages will be authored in InstallShield. We will use whatever feature Installshield offers (IIS integration, COM registration, Registry, etc). The dialog's created by InstallShield will not be used (that is what the bootstrapper is for). The MSIs will be installed silently.
B. Whenever we need to write CA's for stuff that InstallShield can't handle, we will be writing them in managed code (C#) using DTF. We will be creating a "Custom Action Framework" that will "standardize" how we use custom actions.
C. We will create a custom bootstrapper (the "setup.exe") in C# to "handle" the installation.
We have decided to go with a multiple MSI approach and use MSI transaction to "chain" the installation from the boostrapper (inspired from Office 2007 installer)
The boostrapper that we are envisioning to create is inspired from Visual Studio's and SQL Server's bootstrapper. The boostrapper will be responsible for the following:
Prerequisite installation: Each application require a pre-requisite. These pre-requisites are listed in an XML file placed on the same folder as the MSI (inspired from Office 2007 installer) along with other metadata. Depending on current state of the system, the boostrapper will decide which pre-requisite to be installed or not.
Feature selection: We are planning to structure the "internal" MSI's feature in such a way that it will not be appropriate to be displayed right away to the end-user. We will have feature labeled as "Core_Files", or "Vista_Only" or "64bit_Only". Depending on the metadata on the XML file (on item 1) and the target system, the bootstrapper will be responsible in "populating" a "feature tree" that the user can customize (also inspired from Office 2007 bootstrapper).
Pre-installation Checks: The bootstrapper will be responsible in checking if the system is ready to receive the installation. For instance, if a machine needs to reboot prior to installation or if the user needs to manually install a service pack, patch or a windows component. Anything that needs to be done that needs user intervention should be displayed here. Think of it as a check list (a listbox) with checks and exes. (Inspired from SQL server's bootstrapper). The "rules" will be written in C#.
Application Configuration: For application that needs to be "configured" prior to installation. These "parameters" (user configuration) will be passed to the respective MSI via MSI Properties.
Actual Installation: The bootstrapper will then perform the installation. Proper "transaction" should be observed when necessary. All "products" that should be grouped together shall be displayed as one product in Add/Remove Programs (by messing with the ARP entries). Also, proper progress shall be reported by each MSI being installed.
-- That's what we have so far.
I think there are a couple of out-of-the-box solutions for creating a custom bootstrapper like dotNetInstaller and BMG. We've look into it but it's not as flexible as we've hoped. There's also BURN but we're not sure if it's ready for primetime.
So here we are... we've decided to create our own custom bootstrapper.
Question:
Are we crazy? Shouldn't we be creating our own bootstrapper? Which ideas listed above are not realistic? Is there a better approach?
Any input regarding our situation will be greatly appreciated. Also, if you have any questions, please don't hesitate to ask.
Frankly, Burn isn't going to be done for at least a year. You already have InstallShield and IMO it has the best off the shelf bootstrapper currently available. I'd scope your requirements back and make it fit the box. Pretty much everything I read from you can be done using InstallShield if you learn to push it to it's limits.
I would go for Burn anyway or some already existing solution.
I'm sure that after some time you'll face new problems that you can't now really imagine.
If you face them, that means that Burn's developers have already faced them and probably got them solved. If not, Burn has a large community that will fix the potential bug faster than you.
Focus on the software you're developing, not on writing installer/bootstrapper.
If I were in your shoes, I would give a burn a try. I'd get me a couple of days and see if it meets my requirements.
I have been look around for Free/Open Source ASP.NET CMS / Portal systems for a while now, and have seived it down to two different ones.
Umbraco - http://umbraco.org
mojoPortal - http://www.mojoportal.com
Both look excellent and have different appealing features, but I am looking for people who have used both and which one you went with and why??
I actually went for Umbraco in the end and would never look back, its incredibly easy to install and use
To install you can use the web platform installer to install it and the AMAZING amount of free projects you can EASILY install with a couple of clicks make it by far the best CMS out there
http://our.umbraco.org/projects
If you are unsure where to start have a read of this
http://www.blogfodder.co.uk/post/A-Complete-Newbies-Guide-To-Umbraco-CMS.aspx
I tried Umbraco and it is not for the timid. I feel I'm a fairly technical person, Sr. Web Developer... and after several hours I gave up.
MojoPortal just works.
It has its flaws, but the simple fact that it just works means it wins.
I used Kentico, DNN, Sitecore, Joomla, CMS Made Simple (Yes admittedly not mojoPortal). Umbraco is by far the most powerful if you are after a highly customised and highly specified solution. Linq2Umbraco just seals the deal.
However, if you are after idiot proof CMS with everything built in, and your biggest concern is to look for check boxes to enable forum/blogs/whatever other joke modules/bells and whistles/etc. Umbraco isn't for you. IMO Kentico/DNN are the ones.
Edit - And 3 years later, I've used SharePoint, epiServer, SiteFinity as well.
Umbraco still wins hands down.
mojoPortal seems easier to use to me and it works even with javascript disabled like using noscript browser plugin. Seems more care of accessibility has been taken using progressive enhancement javascript techniques whereas you can't manage your site at all with javascript disabled using Umbraco.
I haven't tried mojoPortal, but I love Umbraco.
Things I like:
Clean code
Uses XSLT, python, or .NET to extend
Awesome community support
Tutorial videos for easy learning
Admin area is extensible
Good plug-in projects
But really its because I can use it for both small and large projects easily.