mstaton
Posts: 17
Joined: Wed Apr 22, 2009 2:24 pm

AI vs. Visual Studio Deployment Projects

There is a discussion on our team about whether it is better to use the built-in Visual Studio deployment projects. I believe that that AI is better but could use some help giving reasons why. We have a large product with many sub projects, so anything we do is complex and takes time. We are currently using Visual Studio deployment projects but need to make some major changes to the installer.

One reason for me is that the deployment projects do not save your excludes, so you have to redo excludes each time.

Any suggestions?
alavoler
Posts: 45
Joined: Thu Mar 12, 2009 4:29 pm
Location: France
Contact: Website

Re: AI vs. Visual Studio Deployment Projects

Hi,

Without mentioning other products, AI is really the one I found the best to not very expensive! I advice you, just download the trial version to this.

In addition, output versions are frequent, and those dealing with the product seem to be listening to the consumer!

Compared to the VS Setup project, it has nothing to do:
- There is a dialog designer easy to use (when VS offers 3 dialogs possible ....)
- You can control use input dialog with VbScript
- You can refresh the directory Build (VS can not even handle recursive deletion of a directory!)
- Management of sql script, deployment on IIS ...
- Anything we can do in VS Setup Project you can do it in AI, in better! (custom action ...) (no regrets)
- AI is UserFriendly :) and It is well thought
- And many others features... (multilanguage, dynamic variable, drivers, firewall...)

VS setup project is perfect for small applications (copy / paste / uninstall), it is perfectly integrated into VS. But when we want to do something special, it becomes hell!

Have a nice day
mstaton
Posts: 17
Joined: Wed Apr 22, 2009 2:24 pm

Re: AI vs. Visual Studio Deployment Projects

Thank you alavoler.

I should mention that one point of contention is that VS setup projects automatically add files for dependencies. There are some that are concerned that if we switch to AI, we could add a file that has dependencies and possibly fail to add those dependencies. Perhaps a missing file would only be required in some cases, making it harder to find in testing, creating the possibility that a user could eventually have a file missing exception. What is the best way in AI make sure an install build is not missing dependencies?

Thanks!
alavoler
Posts: 45
Joined: Thu Mar 12, 2009 4:29 pm
Location: France
Contact: Website

Re: AI vs. Visual Studio Deployment Projects

Indeed, it is an excellent question!

I will try to answer them as best as possible, but developers of AI might be a better solution ...

I do not think AI manage dependencies (alas), but it is always possible to create a Setup Project in Visual Studio and import the MSI created by it!

As a result (I have tested) there is no worry, all the dependencies of the project are imported and no oversight is committed.


This is not the most integrated solutions, but it allows sensor dependencies VS (the only good thing in a VS setup Project in effect)
mstaton
Posts: 17
Joined: Wed Apr 22, 2009 2:24 pm

Re: AI vs. Visual Studio Deployment Projects

Good suggestion. That may be our workaround. Thanks!
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: AI vs. Visual Studio Deployment Projects

Hi,

Currently Advanced Installer can add the dependencies of a file only through the Add Dependencies... context menu in the "Files and Folders" page. However, we have on our TODO list an improvement which will make Advanced Installer automatically add the dependencies for all files.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”