Re: Issue with Include Script Command

From: TerryM (nospam_at_hotmail.com)
Date: 06/16/04 

Date: Wed, 16 Jun 2004 13:56:11 -0400

Great info.

Could you pass or restate the variables in the lower includes?For example,
may do a set x = %x% in each level to help pass it along?

Terry

"Rick Fleming" <rfleming@discussions.microsoft.com> wrote in message
news:1d57501c453c9$bc682410$a501280a@phx.gbl...
> Thanks for the reply :),
>
> Well, I did try out the newer version on a test box, and
> it has the same problems. I wrote a simple test set of
> includes and found the following (happens on both
> versions of SMS Installer):
>
> Seems as though, while you can include recursively,
> inside the 3'rd level of includes it 'forgets' compiler
> variables, for instance:
>
> Base (includes %_COMPVAR_%\include\01.ipf), Success
> 01 (includes %_COMPVAR_%\include\02.ipf), Success
> 02 (includes %_COMPVAR_%\include\03.ipf), Failed
>
> However, when you hard code paths (no variables), it
> works indefinately ( I tried up to 6 levels at least)...
>
> Also, in the example I did, I wrapped the following
> around the include in the 01.ipf:
>
> Compiler If File Exist (file that doesn't exist)
>
> And it ignored the compiler statement, and included
> 02.ipf anyway.
>
> I did a search on MS Knowledge Base, but I didn't find
> any articles on either problem, I haven't looked at
> myitforum.com yet (for this specific issue). I did find
> in the archives of this newsgroup a similiar posting from
> 2002, but noone ever replied to them:
>
> http://groups.google.com/groups?
> q=limit+group:microsoft.public.sms.installer&hl=en&lr=&ie=
> UTF-8&group=microsoft.public.sms.installer&selm=usW6%
> 24d2xBHA.2228%40tkmsftngp05&rnum=2
>
>
> Again, thanks for your help so far, it is much
> appreciated :),
>
> Thanks,
> Rick Fleming
>
>
>
> >-----Original Message-----
> >Well, I'm not sure I've ever done multiple includes
> within includes... not
> >sure if this is addressed in the later version but I
> would say you should
> >definitely move to the latest version. Have you checked
> out MS knowledge
> >base, or myitforum.com to see if there are articles on
> the latest version of
> >SMS Installer?
> >
> >But with the issues you have I would say it would hurt
> to at least put the
> >new version of SMSI someplace (maybe a test machine) and
> try it with your
> >script to see what happens.
> >
> >Terry
> >
> >"Rick Fleming" <rfleming@discussions.microsoft.com>
> wrote in message
> >news:1d49d01c453bd$4c5e0150$a101280a@phx.gbl...
> >> Hello,
> >>
> >> I have a 'template framework' for creating automated
> >> silent issuance packages. Based on what files are put
> >> into a specific subfolder of the location of a main IPF
> >> folder, it will build a package based on the content of
> >> the files... for example: if the source of the
> package
> >> is a Microsoft OS Update, it will automatically know
> what
> >> it is and how to run...
> >>
> >> My problem is I have been cleaning up my template code,
> >> and I am running into two problems,
> >>
> >> 1. I have includes within includes, which never caused
> a
> >> problem for me before, but now all of a sudden, SMS
> >> Installer doesn't recognize "Compiler If" statements...
> >> for instance the following:
> >>
> >> If Compiler Variable File
> >> Exists ".\beforeactionevent.ipf" Start Block
> >> Include Script ".\beforeactionevent.ipf"
> >> Compiler Variable End Block
> >>
> >> SMS Installer, upon Compile, will error with "The
> include
> >> script .\beforeactionevent.ipf" could not be opened,
> even
> >> though I am checking to ensure it exists before I allow
> >> the compiler to place that statement into the source.
> >>
> >> If I place a blank script at that location, it will
> pass
> >> it fine. If it is in the main script (with or without
> >> the blank referenced file), it works fine.
> >>
> >>
> >> 2. Also, if you have a compiler variable which points
> to
> >> the root of your 'includes' location, ex: _INCLOC_,
> and
> >> this variable is also defined in later includes, does
> the
> >> later includes override the main issuance defination of
> >> the compiler variable?
> >>
> >> My script seems to 'forget' what the value of the
> >> compiler variable is after a few levels of includes,
> >> becuase it fails to include other includes (which use
> the
> >> compiler variable) after traversing a few levels down
> (in
> >> the include 'tree').
> >>
> >> I receive the same error as the prior one, except it
> >> says "%_INCLOC_%\includes\v2.0\Part1\pre-check.ipf"
> >> instead of the full path. I haven't had an issue doing
> >> this before.
> >>
> >>
> >> I am on version 2.0.91 (unable to move to a later
> version
> >> at this time, is there a definative list of bugs fixed
> >> for the newer 2.0.148?)
> >>
> >>
> >> Thanks in advance for the help :),
> >> Thanks,
> >> Rick Fleming
> >>
> >
> >
> >.
> >

Relevant Pages
Quantcast