Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

More details about J# redistributable package installation in VS 2005 setup

More details about J# redistributable package installation in VS 2005 setup

  • Comments 4

Now that Visual Studio 2005 has shipped, I've gotten a couple of questions from customers wondering why they are able to uncheck the J# language tools item in the Visual Studio setup tree and yet setup still installs the J# redistributable package 2.0.  I partially addressed this issue in a previous blog post back when VS 2005 beta 2 shipped.  The same underlying design that I described in that post exists in the final release of VS 2005.  Essentially, the algorithm for deciding whether or not to install the J# redistributable is the following:

  1. Setup looks at the file baseline.dat and finds the J# redistributable package 2.0 item represented by the section titled [gencomp68]
  2. The [gencomp68] section contains the value ComponentType=3, which means that it is a chained package that will be conditionally installed after the main VS 2005 MSI depending on what features are chosen in the setup feature tree
  3. The [gencomp68] section contains a list of GUIDs in the value DependentFeatures that represent FeatureID values in the Feature table of the main vs_setup.msi
  4. Setup iterates over that list of GUIDs and if it detects that any of the features represented by those GUIDs are selected to be installed as part of VS 2005, it adds the J# redistributable package v2.0 to the list of items that need to be installed after the main VS 2005 MSI is done installing

Now, if you take a look at the baseline.dat file in a text editor and locate the list of GUIDs, you can search for those values in the Feature table of the VS 2005 MSI, you can see that if the J# or Visual Web Developer language tools features are selected during setup, the J# redistributable will also be installed for you as a chained component.

The next question that has come up is one that I haven't addressed in that previous blog post - why does Visual Web Developer require the J# redistributable?  At a high level, the answer is that you are able to develop web applications in any number of programming languages, including J#, so therefore the J# redistributable is installed in case you decide to develop your web applications in J#.

That answer leads to one additional question - why can't you just install Visual Web Developer C# support or something like that if you know ahead of time that you are not planning to develop web applications in J#.  If you look at the feature tree for VS 2005 setup, you will see a single item under Language Tools named Visual Web Developer.  However, this feature is not sub-divided any further, so it is not currently possible to install only the pieces required to install Visual Web Developer C# support, Visual Web Developer VB support, Visual Web Developer J# support, etc.  We determined while developing VS 2005 that it would be very time-intensive and error-prone to try to sub-divide the Visual Web Developer features on a language-by-language basis, and that it would only have questionable benefit to the end user.  Therefore, we had to make a trade-off and the decision was made to live with the side effect of installing the J# redistributable package if the user chooses to install Visual Web Developer during VS 2005 setup (even if the user does not choose to install the J# language tools).  Essentially, we decided that the benefit was not worth the cost, and that we had already noticeably improved the setup behavior related to the J# redistributable from the VS 2003 product (I described the VS 2003 behavior and the background behind why it behaved that way in this post).

 

  • Yes... but did you factor in the cost to us poor schmucks who end up having problems with the J# redistributable install? Of course not!

    See: http://discuss.joelonsoftware.com/default.asp?joel.3.252772.2
  • Hi Matt - we definitely factored that cost in as part of what we were trading off. Unfortunately there are always cases where a setup package will fail. In general, we have found the J# redist setup to be very reliable, and we have found the 2.0 setup to be more reliable than the 1.1 setup.

    The case mentioned in your link is from the J# redist 1.1, but the underlying concern about J# redist setup failing is still valid for 2.0.

    I'm not sure if you were the one who posted that, so if it is you please contact me at aaronste@microsoft.com and I can help you resolve the problem and get the J# redist to install correctly.
  • so...can i now safely uninstall it without repurcussions?
  • Ever since I started using VS 2003, one thing that always ticked me off was why the J# redistributable

Page 1 of 1 (4 items)
Leave a Comment
  • Please add 3 and 5 and type the answer here:
  • Post