In some cases over the years I have found them using VC Runtime builds that apparently never appeared on Microsoft’s public download sites. Autodesk loves to use names, like “VC++ 2008 SP1” that isn’t exactly the same version you’ll find on the internet with that name. Especially with the VCRuntimes, it is important to use the version that they provide. By looking at the prerequisite’s section, I can find the version of the installer they would have used (typically under a folder called 3rdParty). Those VCRuntimes are things I still prefer to keep out of my packages anyway. WMF and MSXML6 were App-V 5 prerequisites and will already be present. Only DOTNET45, DOTNET45LANG, and DIRECTX are incompatible with the current sequencer. Typically the installer doesn’t first check to see if it is already present, so I prefer to remove the entry as a prerequisite as shown above. Some, like IE just check to see if you have internet explorer and bomb out if it isn’t present. If you want to know what any of the dependencies are, you locate that section and look at its lines. POSTREQUISITE=ACAD_PSPACK ACADSKETCHUPIMPORT #PREREQUISITE=ACAD_VISTA_BLOCK IE SSE2 DOTNET45 DOTNET45LANG VCREDIST2008SP1X86 VCREDIST2008SP1X64 VCREDIST2010SP1X86 VCREDIST2010SP1X64 VCREDIST2012X86UPD4 VCREDIST2012X64UPD4 DIRECTX MSXML6 WMF95X64 CM CMILB SNAP_PRE I then just remove items from the list that I want to treat as dependencies. I make a copy of the PREREQUISITE line and comment out the old copy (lines starting with a “#” are comments). This variable defines other sections that are to be installed before installing the software named in the EXE_PATH variable in the section. Inside a section, such as the section, will be a variable called “PREREQUISITE”. UI_SEQUENCE=LaunchDlg BeginDeploymentDlg LicenseDlg ProductInfoDlg ProductSelectionDlg2 ACAD CADM SNAP ADSYNC ADAPPLICATIONMANAGER FullProgressDlg InstallCompleteDlg DeploymentCompleteDlg DeploymentFailedDlg INSTALL_SEQUENCE=NLM CADM SNAP ACAD AUTODESK_RECAP ACADAPPMGR ACADFEATUREDAPPS PERFORMANCETOOL GLUE_PLUGIN_AUT ADSYNC ADAPPLICATIONMANAGER #= Install Execute & UI Sequence =ĮXE_SEQUENCE=ACAD NLM CADM SNAP AUTODESK_RECAP ACADAPPMGR ACADFEATUREDAPPS PERFORMANCETOOL GLUE_PLUGIN_AUT ADSYNC ADAPPLICATIONMANAGER I simply ignore these and make all fixes in the sections themselves. Depending on how you start the installer, one of these is used, and it identifies which of the remaining sections will be run. There are several lines that set variables like “EXE_SEQUENCE”. You start in the section at the top of the file. A section starts with a line contained in square brackets, such as. Make a backup copy of it and then edit the setup.ini file using your favorite text editor like Notepad. To configure the installer, which will be a setup.exe, you modify the setup.ini file. You then treat them as dependencies to be installed on the sequencer prior to sequencing, and pushed out to any client machines natively that are going to get the working package. These must be identified and the installer configured to not install them. There are some dependencies that are incompatible with App-V, and others that are inconvenient. The first thing you do with any Autodesk product is deal with the dependencies. So on a whim I pulled out App-V 5.0 SP2 with Hotfix 4 and AutoCAD 2015 and went to work in a pissed off mood. I worked a trouble ticket with Microsoft for one customer for about 9 months before we gave up in frustration. The app would launch and immediately spit out an application specific error that it was not installed properly, and all of the procmons and xperfs could not help. ![]() This was against a 4.6 sequencer, but testing against the new 5.0 showed the same symptom. Then some versions of the 2013 series, like Revit and Creation Suite seemed to have the same kind of launch issue. The first Autodesk version I ran into with a seemingly unsolvable problem was AutoCAD Architecture 2012. And sometimes we struggle with how to make that work for a couple weeks, but it always does. Over the years, the software designers at AutoDesk are seemingly always using some cutting edge developer stuff inside their annual releases. But it was still big and hairy and it took more than a few passes to get it right. They didn’t have as many versions back then, I recall just one version of AutoCAD plus 3DS Max. Autodesk was one of the early ISVs to really get in and support the concept of virtualizing applications. I first sequenced the 2000i version of AutoCAD back in 2001. Feeling rather pissed off, I decided to work on something horrible. Then my knee acted up so I needed to give it a couple days of rest. And great summer weather was set for a great week of golf. The stars had aligned! I had finished all of the testing for The Deployment Performance Series research, published the first of the 8 papers, shipped my server down to North Carolina for our next training class.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |